Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c5656dabe85aaba8622d2aa1eb39d50279d7bac9a8ed1da8657a7bca56cf684

Tx prefix hash: 61810030fbb2c8256035bbf9eb2c425ff06c0ea130fa02a4301641fdeda8a5f5
Tx public key: ae238680ef92d5c041e3c4f772bc2de81e5381cb0863f9fb3c3b567bb6aef787
Timestamp: 1710777303 Timestamp [UCT]: 2024-03-18 15:55:03 Age [y:d:h:m:s]: 01:071:05:55:29
Block: 981110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311928 RingCT/type: yes/0
Extra: 01ae238680ef92d5c041e3c4f772bc2de81e5381cb0863f9fb3c3b567bb6aef78702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 128fb3bce710101d01e8692b52be062ceb220555b7b4e729b6e67904070f4525 0.600000000000 1441203 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": 981120, "vin": [ { "gen": { "height": 981110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "128fb3bce710101d01e8692b52be062ceb220555b7b4e729b6e67904070f4525" } } ], "extra": [ 1, 174, 35, 134, 128, 239, 146, 213, 192, 65, 227, 196, 247, 114, 188, 45, 232, 30, 83, 129, 203, 8, 99, 249, 251, 60, 59, 86, 123, 182, 174, 247, 135, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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