Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef616b579ccc529b7b09c7592adc5e9d308fcb86ab55abfc88b2d6a81b1ca406

Tx prefix hash: ef555596c6591e2670dd59e67d5911109a0d3eb40eaee6bcceac02052567dfce
Tx public key: 51e9ae1e22dd6747428cc4c938b4723c4847c9a2334f2ccd9c4d578367d0518e
Timestamp: 1745843105 Timestamp [UCT]: 2025-04-28 12:25:05 Age [y:d:h:m:s]: 00:009:22:34:32
Block: 1271295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7108 RingCT/type: yes/0
Extra: 0151e9ae1e22dd6747428cc4c938b4723c4847c9a2334f2ccd9c4d578367d0518e02110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8403b74d06fd7fb8d27d4517f1ee12b5287d26ebb60b585bd78dbeae37bb53f1 0.600000000000 1758554 of 15

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": 1271305, "vin": [ { "gen": { "height": 1271295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8403b74d06fd7fb8d27d4517f1ee12b5287d26ebb60b585bd78dbeae37bb53f1" } } ], "extra": [ 1, 81, 233, 174, 30, 34, 221, 103, 71, 66, 140, 196, 201, 56, 180, 114, 60, 72, 71, 201, 162, 51, 79, 44, 205, 156, 77, 87, 131, 103, 208, 81, 142, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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