Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d42e1d1c6ee74025133825630fae7e9e75eedfc7378d2fab496fddd7c0d50c

Tx prefix hash: c863e4c80381371d9efa84c76b1e44dec640824970eab3c8aba4ff6a73ee694b
Tx public key: 670bed85a24ad7c5b8741ad524352a5a8a79512d76dbf5aa7472d8e34743a449
Timestamp: 1574660041 Timestamp [UCT]: 2019-11-25 05:34:01 Age [y:d:h:m:s]: 05:035:21:34:09
Block: 16943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168500 RingCT/type: yes/0
Extra: 01670bed85a24ad7c5b8741ad524352a5a8a79512d76dbf5aa7472d8e34743a449021100000001b63f0b49000000000000000000

1 output(s) for total of 539.377700307000 dcy

stealth address amount amount idx
00: ec979cbaf03c0fc6007b9fb468e48efbe2426b2ecf93239ae6647f37527bd1a6 539.377700307000 24137 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": 16953, "vin": [ { "gen": { "height": 16943 } } ], "vout": [ { "amount": 539377700307, "target": { "key": "ec979cbaf03c0fc6007b9fb468e48efbe2426b2ecf93239ae6647f37527bd1a6" } } ], "extra": [ 1, 103, 11, 237, 133, 162, 74, 215, 197, 184, 116, 26, 213, 36, 53, 42, 90, 138, 121, 81, 45, 118, 219, 245, 170, 116, 114, 216, 227, 71, 67, 164, 73, 2, 17, 0, 0, 0, 1, 182, 63, 11, 73, 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