Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8edd363e23cb869ac77b3b1eb248baa3df3ee39f3ca9aa38b717a3acc1be56e3

Tx prefix hash: c4b7fed9c87e64aefd2808cf4d5c91a87937ca31cf9bde1c93c706626a3baf8c
Tx public key: 40eaf5a10c7de09a30225986012648c797fac8b7a24330db4177dbddc961bbda
Timestamp: 1578764809 Timestamp [UCT]: 2020-01-11 17:46:49 Age [y:d:h:m:s]: 05:098:00:56:11
Block: 43352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220241 RingCT/type: yes/0
Extra: 0140eaf5a10c7de09a30225986012648c797fac8b7a24330db4177dbddc961bbda0211000000128a2ee0d9000000000000000000

1 output(s) for total of 440.917839246000 dcy

stealth address amount amount idx
00: 8144aa66deb82911d2416038b3f1be0f0c706e036687073162d2122862b2a5e6 440.917839246000 78483 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": 43362, "vin": [ { "gen": { "height": 43352 } } ], "vout": [ { "amount": 440917839246, "target": { "key": "8144aa66deb82911d2416038b3f1be0f0c706e036687073162d2122862b2a5e6" } } ], "extra": [ 1, 64, 234, 245, 161, 12, 125, 224, 154, 48, 34, 89, 134, 1, 38, 72, 199, 151, 250, 200, 183, 162, 67, 48, 219, 65, 119, 219, 221, 201, 97, 187, 218, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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