Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d6762e8984191461ecce5bf9b730692f905138b40f57074ce13d3e78a8460b

Tx prefix hash: 7792691e6bfd3a52b9a0c42dde8112d9c220197f360f283e6d67f5641658f6f8
Tx public key: e8b977b23aa953b196f31f2bbf6fc0878c5acb2a1ebb48193c1f9fdb31bb94fc
Timestamp: 1696061558 Timestamp [UCT]: 2023-09-30 08:12:38 Age [y:d:h:m:s]: 02:054:02:36:07
Block: 859305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558305 RingCT/type: yes/0
Extra: 01e8b977b23aa953b196f31f2bbf6fc0878c5acb2a1ebb48193c1f9fdb31bb94fc021100000001faf35c9c000000000000000000

1 output(s) for total of 0.872500860000 dcy

stealth address amount amount idx
00: 60d17ff1c23f2f28b524808444d2fefe1ebb9306c80d539d96b6a4e08dfac7a5 0.872500860000 1313525 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": 859315, "vin": [ { "gen": { "height": 859305 } } ], "vout": [ { "amount": 872500860, "target": { "key": "60d17ff1c23f2f28b524808444d2fefe1ebb9306c80d539d96b6a4e08dfac7a5" } } ], "extra": [ 1, 232, 185, 119, 178, 58, 169, 83, 177, 150, 243, 31, 43, 191, 111, 192, 135, 140, 90, 203, 42, 30, 187, 72, 25, 60, 31, 159, 219, 49, 187, 148, 252, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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