Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a69c1073029592e155c7dbc47228e1640904db4d0c6120555919ee35b7c63bdd

Tx prefix hash: 8fe3ed5f7673969b7dfbfc86089a2aefcc2c0f52893362bac24e3fa11fe4b104
Tx public key: 324b06301abd0d38c1a42d2ed1d5fe41e2d5ba84d0fb2264567ae940646c60e6
Timestamp: 1730629139 Timestamp [UCT]: 2024-11-03 10:18:59 Age [y:d:h:m:s]: 00:145:19:42:22
Block: 1145596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104045 RingCT/type: yes/0
Extra: 01324b06301abd0d38c1a42d2ed1d5fe41e2d5ba84d0fb2264567ae940646c60e60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df63f987771a65dcee05536010b483841a6d7face386013f9ea8d650c0a2902 0.600000000000 1630065 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": 1145606, "vin": [ { "gen": { "height": 1145596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df63f987771a65dcee05536010b483841a6d7face386013f9ea8d650c0a2902" } } ], "extra": [ 1, 50, 75, 6, 48, 26, 189, 13, 56, 193, 164, 45, 46, 209, 213, 254, 65, 226, 213, 186, 132, 208, 251, 34, 100, 86, 122, 233, 64, 100, 108, 96, 230, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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