Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859db3088bc78b8822f3bb79eb5a5d33d47ce4949c62ca0f0a139d46028954dd

Tx prefix hash: 46c22e632b2ab73aac5523ae3592df621b496479ac3799f923a09d104052ab64
Tx public key: c536ee7f74aff4e5af229a6a7149a2c15bb70b6ab78d01beb4bf1b2b747e93c2
Timestamp: 1713917103 Timestamp [UCT]: 2024-04-24 00:05:03 Age [y:d:h:m:s]: 00:204:18:53:48
Block: 1007122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146600 RingCT/type: yes/0
Extra: 01c536ee7f74aff4e5af229a6a7149a2c15bb70b6ab78d01beb4bf1b2b747e93c20211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b37d1c0772b5ed08c874e7f23e1e866ce4f1452a3802cca83e4c4139af532cff 0.600000000000 1468364 of 15

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": 1007132, "vin": [ { "gen": { "height": 1007122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b37d1c0772b5ed08c874e7f23e1e866ce4f1452a3802cca83e4c4139af532cff" } } ], "extra": [ 1, 197, 54, 238, 127, 116, 175, 244, 229, 175, 34, 154, 106, 113, 73, 162, 193, 91, 183, 11, 106, 183, 141, 1, 190, 180, 191, 27, 43, 116, 126, 147, 194, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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