Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5d9222b13bcb128cfe80fe874f023da6ca6cd7a48672c205ca9cd97207e38c

Tx prefix hash: 05dcef17d621a127a0e87ccf7884fb3a708e0c338555e3f4d24c59803acbf7ca
Tx public key: a103b11c8c9d8d29046f5cd5ab9a206c38cb8e83216eb05278ab1a26b337bd32
Timestamp: 1653347419 Timestamp [UCT]: 2022-05-23 23:10:19 Age [y:d:h:m:s]: 02:357:17:50:38
Block: 507485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776102 RingCT/type: yes/0
Extra: 01a103b11c8c9d8d29046f5cd5ab9a206c38cb8e83216eb05278ab1a26b337bd3202110000000ec9067537000000000000000000

1 output(s) for total of 12.778848534000 dcy

stealth address amount amount idx
00: db1ae4f4b6b6aed869790051b8f4d8ce05766e338ccd43700b43eeeb1b7f9ffa 12.778848534000 933242 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": 507495, "vin": [ { "gen": { "height": 507485 } } ], "vout": [ { "amount": 12778848534, "target": { "key": "db1ae4f4b6b6aed869790051b8f4d8ce05766e338ccd43700b43eeeb1b7f9ffa" } } ], "extra": [ 1, 161, 3, 177, 28, 140, 157, 141, 41, 4, 111, 92, 213, 171, 154, 32, 108, 56, 203, 142, 131, 33, 110, 176, 82, 120, 171, 26, 38, 179, 55, 189, 50, 2, 17, 0, 0, 0, 14, 201, 6, 117, 55, 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