Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e531cb8150ef9941e19a87505f55834431d74943af310837f47fea044393e4

Tx prefix hash: 9c5e944c66734b845702740bfd7d06699ea8ecc6fa85ebe66d20684b28dc8bc7
Tx public key: e5c67387a3e5ce32a8b7c072b1585430e9f3aeff7a4539f8bb4c8ecb0f15900a
Timestamp: 1636980056 Timestamp [UCT]: 2021-11-15 12:40:56 Age [y:d:h:m:s]: 03:161:01:48:04
Block: 374823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893674 RingCT/type: yes/0
Extra: 01e5c67387a3e5ce32a8b7c072b1585430e9f3aeff7a4539f8bb4c8ecb0f15900a021100000007e9564d6f000000000000000000

1 output(s) for total of 35.160593061000 dcy

stealth address amount amount idx
00: f029272343e67dc9912ee8a304bb7ecb8d3a2a8f007e42e241970025dc8aa518 35.160593061000 758589 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": 374833, "vin": [ { "gen": { "height": 374823 } } ], "vout": [ { "amount": 35160593061, "target": { "key": "f029272343e67dc9912ee8a304bb7ecb8d3a2a8f007e42e241970025dc8aa518" } } ], "extra": [ 1, 229, 198, 115, 135, 163, 229, 206, 50, 168, 183, 192, 114, 177, 88, 84, 48, 233, 243, 174, 255, 122, 69, 57, 248, 187, 76, 142, 203, 15, 21, 144, 10, 2, 17, 0, 0, 0, 7, 233, 86, 77, 111, 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