Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5752655e826add0daad869d29fcb3fc3fb1b86b6ee7c476ee7230356f43ffd0

Tx prefix hash: 38518f26f6b7fb76cdc24a53dde221b3ef857f2912a99ada41771ce3f6a7f494
Tx public key: ce48c4dd7579a2b3a355b103cc110826cd032b674ddab13539620f9b63a0dbf4
Timestamp: 1742158167 Timestamp [UCT]: 2025-03-16 20:49:27 Age [y:d:h:m:s]: 00:239:07:53:27
Block: 1240807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168752 RingCT/type: yes/0
Extra: 01ce48c4dd7579a2b3a355b103cc110826cd032b674ddab13539620f9b63a0dbf40211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e683e043d40bf2e80b043a65c8a6ad784632b1e4aa2ecd6c17521612a30e9079 0.600000000000 1727780 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": 1240817, "vin": [ { "gen": { "height": 1240807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e683e043d40bf2e80b043a65c8a6ad784632b1e4aa2ecd6c17521612a30e9079" } } ], "extra": [ 1, 206, 72, 196, 221, 117, 121, 162, 179, 163, 85, 177, 3, 204, 17, 8, 38, 205, 3, 43, 103, 77, 218, 177, 53, 57, 98, 15, 155, 99, 160, 219, 244, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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