Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 620b49a06d2ba631f33db5bab6dd7e76309f668e8043a9e6ec63140d9a67a5db

Tx prefix hash: db282a7695376ee77ccd9bfa0e89f98b5ba5de723114e47ac842b29a6247d3c6
Tx public key: d79ea7628da33c25c6d722ec296dc9906287676295aff193e5a7b0020858e424
Timestamp: 1732342358 Timestamp [UCT]: 2024-11-23 06:12:38 Age [y:d:h:m:s]: 00:000:23:14:05
Block: 1159781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694 RingCT/type: yes/0
Extra: 01d79ea7628da33c25c6d722ec296dc9906287676295aff193e5a7b0020858e424021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e7b63f8c3b26410fa3c6e8703e9bcce442919f81c1e1f24c7dcf33e73c6edba 0.600000000000 1645420 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": 1159791, "vin": [ { "gen": { "height": 1159781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e7b63f8c3b26410fa3c6e8703e9bcce442919f81c1e1f24c7dcf33e73c6edba" } } ], "extra": [ 1, 215, 158, 167, 98, 141, 163, 60, 37, 198, 215, 34, 236, 41, 109, 201, 144, 98, 135, 103, 98, 149, 175, 241, 147, 229, 167, 176, 2, 8, 88, 228, 36, 2, 17, 0, 0, 0, 3, 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