Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b161bcef9f65911068158844858bdab4d2cf927c627a0ce0e7864f7954d30e6

Tx prefix hash: 2274789eeae243f0f3a1493e52f9b72db0bf0f9d66184e3eb1d582232be1cbed
Tx public key: 8ae53776fab6eb599f0c5a0ffee3d22d7c627c1248231acb4b63aad54a9627d5
Timestamp: 1749677166 Timestamp [UCT]: 2025-06-11 21:26:06 Age [y:d:h:m:s]: 00:151:00:39:09
Block: 1303009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105648 RingCT/type: yes/0
Extra: 018ae53776fab6eb599f0c5a0ffee3d22d7c627c1248231acb4b63aad54a9627d5021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 458bad9b40cb404d1229225d70c89cf0979fa5221d2be534439602cd1aaf539e 0.600000000000 1790584 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": 1303019, "vin": [ { "gen": { "height": 1303009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "458bad9b40cb404d1229225d70c89cf0979fa5221d2be534439602cd1aaf539e" } } ], "extra": [ 1, 138, 229, 55, 118, 250, 182, 235, 89, 159, 12, 90, 15, 254, 227, 210, 45, 124, 98, 124, 18, 72, 35, 26, 203, 75, 99, 170, 213, 74, 150, 39, 213, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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