Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19af9c61725b180151e38bb7a18932e5827b3086a01d5c867fceeb7fc37f3bf5

Tx prefix hash: 88f07a0fc76b094475a88bb54d34760563e2f6de51eb0da4967e29b5ae650bb3
Tx public key: 904f81d4111f1a8d8916dfd395184091a382f3c798391c8d7d0c51aaba9829a5
Timestamp: 1710839102 Timestamp [UCT]: 2024-03-19 09:05:02 Age [y:d:h:m:s]: 00:310:00:22:32
Block: 981631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221839 RingCT/type: yes/0
Extra: 01904f81d4111f1a8d8916dfd395184091a382f3c798391c8d7d0c51aaba9829a50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 476560aa2f3fb485f48d20560edccbafc66c524b77340ad457fd75c8a7f92766 0.600000000000 1441728 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": 981641, "vin": [ { "gen": { "height": 981631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "476560aa2f3fb485f48d20560edccbafc66c524b77340ad457fd75c8a7f92766" } } ], "extra": [ 1, 144, 79, 129, 212, 17, 31, 26, 141, 137, 22, 223, 211, 149, 24, 64, 145, 163, 130, 243, 199, 152, 57, 28, 141, 125, 12, 81, 170, 186, 152, 41, 165, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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