Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda1e33b6a457817c38c1356a97fa09542972dba14e5c950defd42b4de242946

Tx prefix hash: 80b15e8db0afc7eba0a038561f6ccc30aa694145d127502a0d0aaf8fd6ea55f8
Tx public key: 28924e53f6791e5003d81e2afd56f29cadabc2dc02df866186d49969f5beef1a
Timestamp: 1707738784 Timestamp [UCT]: 2024-02-12 11:53:04 Age [y:d:h:m:s]: 01:070:22:17:55
Block: 955900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311743 RingCT/type: yes/0
Extra: 0128924e53f6791e5003d81e2afd56f29cadabc2dc02df866186d49969f5beef1a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3b098c12a85d70f810a126ddcfc874f5ec767f15e919427e1af0c91543d906a 0.600000000000 1415200 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": 955910, "vin": [ { "gen": { "height": 955900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b098c12a85d70f810a126ddcfc874f5ec767f15e919427e1af0c91543d906a" } } ], "extra": [ 1, 40, 146, 78, 83, 246, 121, 30, 80, 3, 216, 30, 42, 253, 86, 242, 156, 173, 171, 194, 220, 2, 223, 134, 97, 134, 212, 153, 105, 245, 190, 239, 26, 2, 17, 0, 0, 0, 1, 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