Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ef56952a592e45cedddca64227adc90c739b72eab705433e358316cb763d40

Tx prefix hash: 3eab20065e0d5cfc4ced66d3c6d36ce1fade884236f598a7afd2c04b5ee0860b
Tx public key: 59b3f3959b4f38c85b3a984dac69b4f9d451b10c3d39bbdfaa410f4627bca35e
Timestamp: 1582972470 Timestamp [UCT]: 2020-02-29 10:34:30 Age [y:d:h:m:s]: 04:315:00:40:16
Block: 73935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118905 RingCT/type: yes/0
Extra: 0159b3f3959b4f38c85b3a984dac69b4f9d451b10c3d39bbdfaa410f4627bca35e021100000006724f989b000000000000000000

1 output(s) for total of 349.159169607000 dcy

stealth address amount amount idx
00: a566fc42ad2f25e87923a75612e49ceb65ed51290342f491f6493712622f12c3 349.159169607000 136634 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": 73945, "vin": [ { "gen": { "height": 73935 } } ], "vout": [ { "amount": 349159169607, "target": { "key": "a566fc42ad2f25e87923a75612e49ceb65ed51290342f491f6493712622f12c3" } } ], "extra": [ 1, 89, 179, 243, 149, 155, 79, 56, 200, 91, 58, 152, 77, 172, 105, 180, 249, 212, 81, 177, 12, 61, 57, 187, 223, 170, 65, 15, 70, 39, 188, 163, 94, 2, 17, 0, 0, 0, 6, 114, 79, 152, 155, 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