Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a43308273f7f70974b450b0012a389c8689a487f25af926ebb4dc1b09ed1e2

Tx prefix hash: 4345e04be6b388980882109653e8afdc1932c74a12aa82bc3588c11f32a2b2ef
Tx public key: dc26f8add4c561a742c4dd72e5b43489f459fbce3df2eb08efc5a5e64effe6a2
Timestamp: 1761860369 Timestamp [UCT]: 2025-10-30 21:39:29 Age [y:d:h:m:s]: 00:009:05:10:14
Block: 1401491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6581 RingCT/type: yes/0
Extra: 01dc26f8add4c561a742c4dd72e5b43489f459fbce3df2eb08efc5a5e64effe6a2021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42b417db60eec4b3aa1e21c18b65d01b43c68d7e9682b1ed1654efcb006be617 0.600000000000 1889810 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": 1401501, "vin": [ { "gen": { "height": 1401491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42b417db60eec4b3aa1e21c18b65d01b43c68d7e9682b1ed1654efcb006be617" } } ], "extra": [ 1, 220, 38, 248, 173, 212, 197, 97, 167, 66, 196, 221, 114, 229, 180, 52, 137, 244, 89, 251, 206, 61, 242, 235, 8, 239, 197, 165, 230, 78, 255, 230, 162, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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