Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20280e11958b8aa9a983b6337111d1501fc9a6205da7b542e4a53f777a8c0523

Tx prefix hash: 23b239319124f68ce12c559b5957aa43e2e13e4ed001748981eafdcf0eaa1846
Tx public key: 8cd2f1acb8bd3e53fb8d2529ed56cbf5e8518afbdc52306eab102efeb1c6bc3d
Timestamp: 1708721728 Timestamp [UCT]: 2024-02-23 20:55:28 Age [y:d:h:m:s]: 00:338:07:22:54
Block: 964056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241931 RingCT/type: yes/0
Extra: 018cd2f1acb8bd3e53fb8d2529ed56cbf5e8518afbdc52306eab102efeb1c6bc3d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bef1a6858943fc748d58661b30ea374f436bb0a7194e8dabdcb968623d02632f 0.600000000000 1423783 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": 964066, "vin": [ { "gen": { "height": 964056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bef1a6858943fc748d58661b30ea374f436bb0a7194e8dabdcb968623d02632f" } } ], "extra": [ 1, 140, 210, 241, 172, 184, 189, 62, 83, 251, 141, 37, 41, 237, 86, 203, 245, 232, 81, 138, 251, 220, 82, 48, 110, 171, 16, 46, 254, 177, 198, 188, 61, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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