Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe66ba044572b73f5a2913b099ca3a7257b96ed14f2903966e05d543fb4ef79

Tx prefix hash: 10d05f5062f78caa1eb489798f31bdb6bdfabe333c57833fb6bfe6a9a20f7b79
Tx public key: 80e283b0b3cf2a7f603f16c80400c0934c08f6128df5a011a5565a048bce7381
Timestamp: 1706759912 Timestamp [UCT]: 2024-02-01 03:58:32 Age [y:d:h:m:s]: 01:068:18:14:25
Block: 947770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310217 RingCT/type: yes/0
Extra: 0180e283b0b3cf2a7f603f16c80400c0934c08f6128df5a011a5565a048bce73810211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3afc598eb800efe644f0442b9837b7b9c0a76a33bf40729bc46eee9a94cb5d8 0.600000000000 1406128 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": 947780, "vin": [ { "gen": { "height": 947770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3afc598eb800efe644f0442b9837b7b9c0a76a33bf40729bc46eee9a94cb5d8" } } ], "extra": [ 1, 128, 226, 131, 176, 179, 207, 42, 127, 96, 63, 22, 200, 4, 0, 192, 147, 76, 8, 246, 18, 141, 245, 160, 17, 165, 86, 90, 4, 139, 206, 115, 129, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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