Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26547ea9d690e57136c3183a38d5dcf5cd56a9f682c16f64f8430186b91fac7a

Tx prefix hash: 4c1dc8f7c0ba9a21114b5d57b73399bb74f6ca49ee8d0d5629067cb118926c05
Tx public key: 21f723a692fd96f75883be57704b32e6795c1638bb166d612712e77cf9962fb9
Timestamp: 1689621760 Timestamp [UCT]: 2023-07-17 19:22:40 Age [y:d:h:m:s]: 01:227:06:25:55
Block: 805970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423502 RingCT/type: yes/0
Extra: 0121f723a692fd96f75883be57704b32e6795c1638bb166d612712e77cf9962fb90211000000214b8f5122000000000000000000

1 output(s) for total of 1.310650619000 dcy

stealth address amount amount idx
00: 02d4c83057a1bc8a6909caaae9a64c0e2772786ad34093212dc23e8b1c779bed 1.310650619000 1257265 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": 805980, "vin": [ { "gen": { "height": 805970 } } ], "vout": [ { "amount": 1310650619, "target": { "key": "02d4c83057a1bc8a6909caaae9a64c0e2772786ad34093212dc23e8b1c779bed" } } ], "extra": [ 1, 33, 247, 35, 166, 146, 253, 150, 247, 88, 131, 190, 87, 112, 75, 50, 230, 121, 92, 22, 56, 187, 22, 109, 97, 39, 18, 231, 124, 249, 150, 47, 185, 2, 17, 0, 0, 0, 33, 75, 143, 81, 34, 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