Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a056c4a184c12034b5f977885ebdcfc762d896f8557fc602b9bf47a607b959b3

Tx prefix hash: fff7a7381ddd33172a1da3decbd3c6a17ff593adbe9816837b722600ecf74cd0
Tx public key: 01bfef132169cc6401b1135d08ce742f4a0f4b0df6f377a67de6b64a7beff5b4
Timestamp: 1580567155 Timestamp [UCT]: 2020-02-01 14:25:55 Age [y:d:h:m:s]: 05:032:18:16:37
Block: 56504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175336 RingCT/type: yes/0
Extra: 0101bfef132169cc6401b1135d08ce742f4a0f4b0df6f377a67de6b64a7beff5b402110000000117786bcf000000000000000000

1 output(s) for total of 398.822466946000 dcy

stealth address amount amount idx
00: a57cab09bb783317f93d887327521c6cf3e51226eed364de5fd9e59c335a5f89 398.822466946000 104221 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": 56514, "vin": [ { "gen": { "height": 56504 } } ], "vout": [ { "amount": 398822466946, "target": { "key": "a57cab09bb783317f93d887327521c6cf3e51226eed364de5fd9e59c335a5f89" } } ], "extra": [ 1, 1, 191, 239, 19, 33, 105, 204, 100, 1, 177, 19, 93, 8, 206, 116, 47, 74, 15, 75, 13, 246, 243, 119, 166, 125, 230, 182, 74, 123, 239, 245, 180, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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