Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0e0a09739937fad0099cf9367a3be1a3635c8433910188c2c8a42acc41c2c75

Tx prefix hash: ed84fdf208f762c43668c79a44094b4fe0626f2ae202b39cc93668427f597063
Tx public key: 9781a71896e775ecc3ad8a9f7e3f1c7b3b6a0d33c6f476696ca74a0bb5d090ce
Timestamp: 1766174661 Timestamp [UCT]: 2025-12-19 20:04:21 Age [y:d:h:m:s]: 00:002:05:38:02
Block: 1437234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1609 RingCT/type: yes/0
Extra: 019781a71896e775ecc3ad8a9f7e3f1c7b3b6a0d33c6f476696ca74a0bb5d090ce02110000000c70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f963ae95546e96542e6475a1954fb6fbed75b40089e99f51fd2ea26542b4dad5 0.600000000000 1926041 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": 1437244, "vin": [ { "gen": { "height": 1437234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f963ae95546e96542e6475a1954fb6fbed75b40089e99f51fd2ea26542b4dad5" } } ], "extra": [ 1, 151, 129, 167, 24, 150, 231, 117, 236, 195, 173, 138, 159, 126, 63, 28, 123, 59, 106, 13, 51, 198, 244, 118, 105, 108, 167, 74, 11, 181, 208, 144, 206, 2, 17, 0, 0, 0, 12, 112, 96, 157, 3, 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