Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de79954ba17979187db309cd3d7f091ef2ff175fc04a0105d2c353d28dfa24a7

Tx prefix hash: e28178f7a36aff8eeef32f216a5d5109f48fc21ae32d68e1e3cadcf963828c7f
Tx public key: 462234ea8fd7b01bb3a58f3a218587de24ce329fd0b3ba3f75a739d1f927894e
Timestamp: 1640146952 Timestamp [UCT]: 2021-12-22 04:22:32 Age [y:d:h:m:s]: 02:342:05:24:51
Block: 400804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762672 RingCT/type: yes/0
Extra: 01462234ea8fd7b01bb3a58f3a218587de24ce329fd0b3ba3f75a739d1f927894e0211000000035e327fe8000000000000000000

1 output(s) for total of 28.838343904000 dcy

stealth address amount amount idx
00: 3ba17b49ed73e6a3653acd61e74e412251ba3785ff53daa085ff586de065cc57 28.838343904000 800285 of 0

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": 400814, "vin": [ { "gen": { "height": 400804 } } ], "vout": [ { "amount": 28838343904, "target": { "key": "3ba17b49ed73e6a3653acd61e74e412251ba3785ff53daa085ff586de065cc57" } } ], "extra": [ 1, 70, 34, 52, 234, 143, 215, 176, 27, 179, 165, 143, 58, 33, 133, 135, 222, 36, 206, 50, 159, 208, 179, 186, 63, 117, 167, 57, 209, 249, 39, 137, 78, 2, 17, 0, 0, 0, 3, 94, 50, 127, 232, 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