Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fa8ae7f23bb0723720fd643fce3930146d3eb7ae26bf74c54e6c2bad6c4ca9b

Tx prefix hash: 97e3aff9064acfa05c2b8778702fed45fdbdf0e192cadc85dc6ea541877a590c
Tx public key: 8b84ac9ca9a1de15c7ad175f9f1367777556903538911d6d2f681f5ec159d2c0
Timestamp: 1648669121 Timestamp [UCT]: 2022-03-30 19:38:41 Age [y:d:h:m:s]: 02:352:15:48:12
Block: 469777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 771470 RingCT/type: yes/0
Extra: 018b84ac9ca9a1de15c7ad175f9f1367777556903538911d6d2f681f5ec159d2c00211000000014da16a3a000000000000000000

1 output(s) for total of 17.038605006000 dcy

stealth address amount amount idx
00: 6a2362c9828041c3fedd34f074b34bf14609e2d5ec66c2f30f121b582145fc1b 17.038605006000 888789 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": 469787, "vin": [ { "gen": { "height": 469777 } } ], "vout": [ { "amount": 17038605006, "target": { "key": "6a2362c9828041c3fedd34f074b34bf14609e2d5ec66c2f30f121b582145fc1b" } } ], "extra": [ 1, 139, 132, 172, 156, 169, 161, 222, 21, 199, 173, 23, 95, 159, 19, 103, 119, 117, 86, 144, 53, 56, 145, 29, 109, 47, 104, 31, 94, 193, 89, 210, 192, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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