Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37118ad70c84e759005e2ba8eca01f0013de5a3d4a4bc6ee408509fe1ec8e44f

Tx prefix hash: e6ac405bbde44b69916e4d27e19d331e310a6c8042b362a6832840bae778100f
Tx public key: e8d3e38d085d661895fc9b2e7f2ec14cf681486b99b8ebca08dfeb2ae6cb2584
Timestamp: 1734671349 Timestamp [UCT]: 2024-12-20 05:09:09 Age [y:d:h:m:s]: 00:108:20:39:21
Block: 1179099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77551 RingCT/type: yes/0
Extra: 01e8d3e38d085d661895fc9b2e7f2ec14cf681486b99b8ebca08dfeb2ae6cb25840211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc50f5dc726d53c2d86cb90eaac3453f9e239d4a3dcf164c0d6e3d161b3a4da6 0.600000000000 1665490 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": 1179109, "vin": [ { "gen": { "height": 1179099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc50f5dc726d53c2d86cb90eaac3453f9e239d4a3dcf164c0d6e3d161b3a4da6" } } ], "extra": [ 1, 232, 211, 227, 141, 8, 93, 102, 24, 149, 252, 155, 46, 127, 46, 193, 76, 246, 129, 72, 107, 153, 184, 235, 202, 8, 223, 235, 42, 230, 203, 37, 132, 2, 17, 0, 0, 0, 1, 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