Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83b18b8b771f5966c645341326cab5e63c2ad489831266d69606d7b9eb063eb0

Tx prefix hash: e55bbed1cb4000b32e436fecf2a0c05e160b6dbe13a5c25b7c5bf3ec64ed0e95
Tx public key: cab8c74d99ad45ecb1d0b6f34e23153863807c9387c6ca9ca064fb72cfc84a33
Timestamp: 1721690844 Timestamp [UCT]: 2024-07-22 23:27:24 Age [y:d:h:m:s]: 00:253:09:36:05
Block: 1071560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181022 RingCT/type: yes/0
Extra: 01cab8c74d99ad45ecb1d0b6f34e23153863807c9387c6ca9ca064fb72cfc84a33021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a7c21a8b232f21690501bfbc5331c3bcf1481c1091a801939a11852f37c14d0 0.600000000000 1543837 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": 1071570, "vin": [ { "gen": { "height": 1071560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a7c21a8b232f21690501bfbc5331c3bcf1481c1091a801939a11852f37c14d0" } } ], "extra": [ 1, 202, 184, 199, 77, 153, 173, 69, 236, 177, 208, 182, 243, 78, 35, 21, 56, 99, 128, 124, 147, 135, 198, 202, 156, 160, 100, 251, 114, 207, 200, 74, 51, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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