Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95d87660bd2f7a1c84148666efc9f3fe0de2b58f05f57dafc47c9e015a2b407

Tx prefix hash: bf6a496bebc24c3b74f9bda58339a43b4b0774325b0983cafa3c4f8145157f0d
Tx public key: 5a40679b301e759af63e1a9bfadeda849c824b4171c14f5568e370d2e1cb75f5
Timestamp: 1734787498 Timestamp [UCT]: 2024-12-21 13:24:58 Age [y:d:h:m:s]: 00:083:11:20:29
Block: 1180059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59428 RingCT/type: yes/0
Extra: 015a40679b301e759af63e1a9bfadeda849c824b4171c14f5568e370d2e1cb75f5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a67035decd12f100aa1734880f35243aaf7daecc85f92950e93f2480dce9e7bf 0.600000000000 1666464 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": 1180069, "vin": [ { "gen": { "height": 1180059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a67035decd12f100aa1734880f35243aaf7daecc85f92950e93f2480dce9e7bf" } } ], "extra": [ 1, 90, 64, 103, 155, 48, 30, 117, 154, 246, 62, 26, 155, 250, 222, 218, 132, 156, 130, 75, 65, 113, 193, 79, 85, 104, 227, 112, 210, 225, 203, 117, 245, 2, 17, 0, 0, 0, 2, 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