Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86299a996c900c844d28817b85ecef847519bc63347d91f4d36071853969e669

Tx prefix hash: 05a3ec4ab5c217570d58c82a559bcd3953ba4c9dc7514a6483b8afcb61934b9f
Tx public key: 3eeb02c666ad84eeb1be7bbe59fb979b641afe6c8c38b51eef3be50375e3585f
Timestamp: 1648840678 Timestamp [UCT]: 2022-04-01 19:17:58 Age [y:d:h:m:s]: 03:023:02:35:13
Block: 471117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 796872 RingCT/type: yes/0
Extra: 013eeb02c666ad84eeb1be7bbe59fb979b641afe6c8c38b51eef3be50375e3585f02110000000c5eb576c5000000000000000000

1 output(s) for total of 16.865299458000 dcy

stealth address amount amount idx
00: 008865a8ef35b2343f3c4fad60a1b5c9794cff1b3f33d2de9a84a5dceebebc56 16.865299458000 890393 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": 471127, "vin": [ { "gen": { "height": 471117 } } ], "vout": [ { "amount": 16865299458, "target": { "key": "008865a8ef35b2343f3c4fad60a1b5c9794cff1b3f33d2de9a84a5dceebebc56" } } ], "extra": [ 1, 62, 235, 2, 198, 102, 173, 132, 238, 177, 190, 123, 190, 89, 251, 151, 155, 100, 26, 254, 108, 140, 56, 181, 30, 239, 59, 229, 3, 117, 227, 88, 95, 2, 17, 0, 0, 0, 12, 94, 181, 118, 197, 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