Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17676f4e168ef3742e079d16939dcd5d9d35dc15ca5518b0721eec10aa4f8c9

Tx prefix hash: 8be248afc38e8045b470fa876f40609e7ab219510abfe6bc944da375a383e060
Tx public key: 0fc9086fb9e9c0aaa9d69c3d4c418760c6baa7ad5ff72b8034fa51c19a1e0e72
Timestamp: 1724270575 Timestamp [UCT]: 2024-08-21 20:02:55 Age [y:d:h:m:s]: 00:251:20:51:48
Block: 1092969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179878 RingCT/type: yes/0
Extra: 010fc9086fb9e9c0aaa9d69c3d4c418760c6baa7ad5ff72b8034fa51c19a1e0e72021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 171f1adecfeb5d67f30346604119c61f301d0814efc0be813b9a77bf4f3602fd 0.600000000000 1567820 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": 1092979, "vin": [ { "gen": { "height": 1092969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171f1adecfeb5d67f30346604119c61f301d0814efc0be813b9a77bf4f3602fd" } } ], "extra": [ 1, 15, 201, 8, 111, 185, 233, 192, 170, 169, 214, 156, 61, 76, 65, 135, 96, 198, 186, 167, 173, 95, 247, 43, 128, 52, 250, 81, 193, 154, 30, 14, 114, 2, 17, 0, 0, 0, 1, 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