Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a60619567ca90e25d1de7054bff56ba0d0e2c36d73068d0a12e9a002d21d83c

Tx prefix hash: 01efc3c0e1c8a8574edec8f1ec0d0cf7bea327330a2482b0026b9d0c57295e67
Tx public key: 915df5924060d2fbdb6aece8d52966f8ffc81cfb505fccfbac22c1162d875ce1
Timestamp: 1764295245 Timestamp [UCT]: 2025-11-28 02:00:45 Age [y:d:h:m:s]: 00:025:14:21:10
Block: 1421655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18314 RingCT/type: yes/0
Extra: 01915df5924060d2fbdb6aece8d52966f8ffc81cfb505fccfbac22c1162d875ce10211000000034e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0ec55631aff3c87b1dd02fffb026b34638ae18bf889b579cfa1c3e2547c8d46 0.600000000000 1910212 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": 1421665, "vin": [ { "gen": { "height": 1421655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ec55631aff3c87b1dd02fffb026b34638ae18bf889b579cfa1c3e2547c8d46" } } ], "extra": [ 1, 145, 93, 245, 146, 64, 96, 210, 251, 219, 106, 236, 232, 213, 41, 102, 248, 255, 200, 28, 251, 80, 95, 204, 251, 172, 34, 193, 22, 45, 135, 92, 225, 2, 17, 0, 0, 0, 3, 78, 123, 252, 9, 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