Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b594a7c21ee9f739b6166668c65e3cda456fb1f6352ca10dc18b9795113f5b5b

Tx prefix hash: 1be8e926a916b9d60f0c7ffb469f4395171d045a8b6c46540f56fc1557dc359c
Tx public key: 8f0d1e77dc5c5c3a85de14c3a042cbe70b51e44564a4120c64b790f87d9b382c
Timestamp: 1762203326 Timestamp [UCT]: 2025-11-03 20:55:26 Age [y:d:h:m:s]: 00:016:20:46:43
Block: 1404313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12076 RingCT/type: yes/0
Extra: 018f0d1e77dc5c5c3a85de14c3a042cbe70b51e44564a4120c64b790f87d9b382c0211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78fe2de70b7025622cff08bf7d191c3ae1f4c1779f1ad11a4dfa26cd5d40fde4 0.600000000000 1892670 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": 1404323, "vin": [ { "gen": { "height": 1404313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78fe2de70b7025622cff08bf7d191c3ae1f4c1779f1ad11a4dfa26cd5d40fde4" } } ], "extra": [ 1, 143, 13, 30, 119, 220, 92, 92, 58, 133, 222, 20, 195, 160, 66, 203, 231, 11, 81, 228, 69, 100, 164, 18, 12, 100, 183, 144, 248, 125, 155, 56, 44, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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