Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71e35b7f49c8d7ef7502dd925a26b1812e0e0f29207bab9adf85dbdbf2189b72

Tx prefix hash: cbf361d312e61cc4c02331c378b9f5065a9b88c4609f6b1a74f82f7ff10127c2
Tx public key: 64913131e9402ae3727326ffadc65328bfa8457a24d73c6f5ec81547091c857c
Timestamp: 1724622009 Timestamp [UCT]: 2024-08-25 21:40:09 Age [y:d:h:m:s]: 00:227:10:48:42
Block: 1095871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162423 RingCT/type: yes/0
Extra: 0164913131e9402ae3727326ffadc65328bfa8457a24d73c6f5ec81547091c857c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcd5f7a1f6efe233ecd3a7a80834e1e635d0b631fc1427e49ba4f291b50f4bd3 0.600000000000 1571054 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": 1095881, "vin": [ { "gen": { "height": 1095871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcd5f7a1f6efe233ecd3a7a80834e1e635d0b631fc1427e49ba4f291b50f4bd3" } } ], "extra": [ 1, 100, 145, 49, 49, 233, 64, 42, 227, 114, 115, 38, 255, 173, 198, 83, 40, 191, 168, 69, 122, 36, 215, 60, 111, 94, 200, 21, 71, 9, 28, 133, 124, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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