Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79e27a0ef11f3249deee5aed98581e975b49cc2b2a3596e65ea4cc3ea24cfcf7

Tx prefix hash: 988805bc8641b954077ec6a5668209f30c145570785924893c8f036240dd5e2f
Tx public key: e0272fb2407dcb7c9e3b091404c5324354c18a2d2e624c9797500274b856ad57
Timestamp: 1648584568 Timestamp [UCT]: 2022-03-29 20:09:28 Age [y:d:h:m:s]: 02:077:01:30:48
Block: 469102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574484 RingCT/type: yes/0
Extra: 01e0272fb2407dcb7c9e3b091404c5324354c18a2d2e624c9797500274b856ad57021100000003a8c141c5000000000000000000

1 output(s) for total of 17.126577782000 dcy

stealth address amount amount idx
00: f1b53a6458adcc799106f3138b19cb2c84d54e5c6431bacc16893746833ec552 17.126577782000 887968 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": 469112, "vin": [ { "gen": { "height": 469102 } } ], "vout": [ { "amount": 17126577782, "target": { "key": "f1b53a6458adcc799106f3138b19cb2c84d54e5c6431bacc16893746833ec552" } } ], "extra": [ 1, 224, 39, 47, 178, 64, 125, 203, 124, 158, 59, 9, 20, 4, 197, 50, 67, 84, 193, 138, 45, 46, 98, 76, 151, 151, 80, 2, 116, 184, 86, 173, 87, 2, 17, 0, 0, 0, 3, 168, 193, 65, 197, 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