Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd8100d8e4839bbe53a69f5b69fcadc4c2051aaf7b0d40f4952157357715a34

Tx prefix hash: e567caacb021bbba115030dad9d46d5d4474c3c0030e7704a05e87cca08a5014
Tx public key: c19c8183e1dcf8063fa84a9b00427fe5a48d4a0ef438a219ff34b5892118f0c6
Timestamp: 1581515215 Timestamp [UCT]: 2020-02-12 13:46:55 Age [y:d:h:m:s]: 04:320:22:32:00
Block: 63453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121549 RingCT/type: yes/0
Extra: 01c19c8183e1dcf8063fa84a9b00427fe5a48d4a0ef438a219ff34b5892118f0c60211000000017adf42d3000000000000000000

1 output(s) for total of 378.228877357000 dcy

stealth address amount amount idx
00: 3a380fc41abefd8b06281dce46d2c16ad84a266b2b0798a0e732a317bd253844 378.228877357000 117009 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": 63463, "vin": [ { "gen": { "height": 63453 } } ], "vout": [ { "amount": 378228877357, "target": { "key": "3a380fc41abefd8b06281dce46d2c16ad84a266b2b0798a0e732a317bd253844" } } ], "extra": [ 1, 193, 156, 129, 131, 225, 220, 248, 6, 63, 168, 74, 155, 0, 66, 127, 229, 164, 141, 74, 14, 244, 56, 162, 25, 255, 52, 181, 137, 33, 24, 240, 198, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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