Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669eb6b40c3a768bf4d6d6aca8bb279896d8f09efb90ad78a6229afb2bbb97c1

Tx prefix hash: 25afb0d8043b4ae5ffd1bbd50878499da6448dc5430492604abb934e9c983bb1
Tx public key: fe86741184e3d19c52fbc9092bc8a79e3036d2dc8f88f910029551e53388277a
Timestamp: 1582035141 Timestamp [UCT]: 2020-02-18 14:12:21 Age [y:d:h:m:s]: 05:235:01:55:10
Block: 67462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1318806 RingCT/type: yes/0
Extra: 01fe86741184e3d19c52fbc9092bc8a79e3036d2dc8f88f910029551e53388277a02110000000156c366d3000000000000000000

1 output(s) for total of 366.835364268000 dcy

stealth address amount amount idx
00: 54b34e2606a2f97dd51e9f200acff41ad0eaf091039ed5ff60b421edd772e1b9 366.835364268000 124315 of 0

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": 67472, "vin": [ { "gen": { "height": 67462 } } ], "vout": [ { "amount": 366835364268, "target": { "key": "54b34e2606a2f97dd51e9f200acff41ad0eaf091039ed5ff60b421edd772e1b9" } } ], "extra": [ 1, 254, 134, 116, 17, 132, 227, 209, 156, 82, 251, 201, 9, 43, 200, 167, 158, 48, 54, 210, 220, 143, 136, 249, 16, 2, 149, 81, 229, 51, 136, 39, 122, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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