Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d88c17ddb1533d4aaa49bfa2d47822a4db4a549950a2fec1b0ac3fb432619dd8

Tx prefix hash: d4d71a25dd95a078223c0a0da172225df1758b12c5e39e07920fa1486f2b5ba2
Tx public key: ecb624d1dcdd335928f1db24e2356283676b33d96ab196d2695980274d3fdaff
Timestamp: 1632362209 Timestamp [UCT]: 2021-09-23 01:56:49 Age [y:d:h:m:s]: 04:039:12:47:02
Block: 339151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1062843 RingCT/type: yes/0
Extra: 01ecb624d1dcdd335928f1db24e2356283676b33d96ab196d2695980274d3fdaff0211000000165410958b000000000000000000

1 output(s) for total of 46.158573855000 dcy

stealth address amount amount idx
00: eecd01c33a9923570cece8d8d325644b489c37eb169503b39e9d085a2ea2e373 46.158573855000 697652 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 339161, "vin": [ { "gen": { "height": 339151 } } ], "vout": [ { "amount": 46158573855, "target": { "key": "eecd01c33a9923570cece8d8d325644b489c37eb169503b39e9d085a2ea2e373" } } ], "extra": [ 1, 236, 182, 36, 209, 220, 221, 51, 89, 40, 241, 219, 36, 226, 53, 98, 131, 103, 107, 51, 217, 106, 177, 150, 210, 105, 89, 128, 39, 77, 63, 218, 255, 2, 17, 0, 0, 0, 22, 84, 16, 149, 139, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8