Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7fe3edc51fe48f93e4afd0ee94defb604aabc802a4cebb7b86f95508b2d989c

Tx prefix hash: 665cc64f14c01bd75c7a261f5f174d568d8575716ce3688945f3803e80b597c9
Tx public key: e72deb21a46d3984f66c28f4bd5b2a47d95a2d1d92a48bf66f9a4c94bc3a8366
Timestamp: 1765924127 Timestamp [UCT]: 2025-12-16 22:28:47 Age [y:d:h:m:s]: 00:024:00:32:12
Block: 1435147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17224 RingCT/type: yes/0
Extra: 01e72deb21a46d3984f66c28f4bd5b2a47d95a2d1d92a48bf66f9a4c94bc3a8366021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23206f9ec43137ff53913872a8bdcfdfbfc52eed6d32e1d4915e2fb2181e95f3 0.600000000000 1923944 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": 1435157, "vin": [ { "gen": { "height": 1435147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23206f9ec43137ff53913872a8bdcfdfbfc52eed6d32e1d4915e2fb2181e95f3" } } ], "extra": [ 1, 231, 45, 235, 33, 164, 109, 57, 132, 246, 108, 40, 244, 189, 91, 42, 71, 217, 90, 45, 29, 146, 164, 139, 246, 111, 154, 76, 148, 188, 58, 131, 102, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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