Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 872c236db54b47a622b7ef642bca0afdd9a5b8c3803326d3cbe3b944ec8a5766

Tx prefix hash: f9d73d63655c5266b490bae8d4c79d899396f34f197bf26bd3a9c84824051d07
Tx public key: a5bb8e95cbcd35456efd9e3f64090e9269e525e7b99831b3d945e28bffb46f08
Timestamp: 1730043787 Timestamp [UCT]: 2024-10-27 15:43:07 Age [y:d:h:m:s]: 00:148:03:23:19
Block: 1140786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105661 RingCT/type: yes/0
Extra: 01a5bb8e95cbcd35456efd9e3f64090e9269e525e7b99831b3d945e28bffb46f0802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db21503731cf1f7542498520c4d22baafd09bfba608c0c6559dd13411d70a3c5 0.600000000000 1624589 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": 1140796, "vin": [ { "gen": { "height": 1140786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db21503731cf1f7542498520c4d22baafd09bfba608c0c6559dd13411d70a3c5" } } ], "extra": [ 1, 165, 187, 142, 149, 203, 205, 53, 69, 110, 253, 158, 63, 100, 9, 14, 146, 105, 229, 37, 231, 185, 152, 49, 179, 217, 69, 226, 139, 255, 180, 111, 8, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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