Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58301ea0ed46e98a3d5d601b9f33494e5452cc5f942a9e38aea357b51c6ddd70

Tx prefix hash: c5c0e04c5cc13cc9a9e0e707b083660cfe3158107374823a2cc245eea12b02d7
Tx public key: 10b854ad7db5ed7a6ba43d39dde9bd7925076ce4cfe1d624cb1da3a1de6b494b
Timestamp: 1735450842 Timestamp [UCT]: 2024-12-29 05:40:42 Age [y:d:h:m:s]: 00:098:07:21:58
Block: 1185518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70045 RingCT/type: yes/0
Extra: 0110b854ad7db5ed7a6ba43d39dde9bd7925076ce4cfe1d624cb1da3a1de6b494b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f34208483d704e3d96be8de806468733737a2cf47b98448f2ad0392dc3ce9add 0.600000000000 1671991 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": 1185528, "vin": [ { "gen": { "height": 1185518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f34208483d704e3d96be8de806468733737a2cf47b98448f2ad0392dc3ce9add" } } ], "extra": [ 1, 16, 184, 84, 173, 125, 181, 237, 122, 107, 164, 61, 57, 221, 233, 189, 121, 37, 7, 108, 228, 207, 225, 214, 36, 203, 29, 163, 161, 222, 107, 73, 75, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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