Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9bfaf2fe14ff8ba2e12e99aba8b3cd596c27b8e9889461f11fd73286345bfc1

Tx prefix hash: b39fe7d52a39eb58d59d57d719d9037ec8b9f785defd2edfa0eeb09a0c516d56
Tx public key: fac0396bb1a1857cca8f0a8e14e906a2c27dd18fb6108d62c99ccceff0721261
Timestamp: 1574259279 Timestamp [UCT]: 2019-11-20 14:14:39 Age [y:d:h:m:s]: 05:345:14:20:55
Block: 13260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1387716 RingCT/type: yes/0
Extra: 01fac0396bb1a1857cca8f0a8e14e906a2c27dd18fb6108d62c99ccceff072126102110000000366a80d00000000000000000000

1 output(s) for total of 554.708731740000 dcy

stealth address amount amount idx
00: 7b0ff6f490dae986c910e502ed627fbf90d6082c3ff8ed4a339754af131ab321 554.708731740000 15479 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": 13270, "vin": [ { "gen": { "height": 13260 } } ], "vout": [ { "amount": 554708731740, "target": { "key": "7b0ff6f490dae986c910e502ed627fbf90d6082c3ff8ed4a339754af131ab321" } } ], "extra": [ 1, 250, 192, 57, 107, 177, 161, 133, 124, 202, 143, 10, 142, 20, 233, 6, 162, 194, 125, 209, 143, 182, 16, 141, 98, 201, 156, 204, 239, 240, 114, 18, 97, 2, 17, 0, 0, 0, 3, 102, 168, 13, 0, 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