Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8710038e0b479c42448ad13cbd7655b8fee362421b658fc33976a0f394e37db5

Tx prefix hash: d85357924486039e6ab0b8b731c999102146cf6a01d6d6f14feccdd531493baa
Tx public key: 3721eef5c4d83668619a03ec1c9cc2c2fa03e74ae4a0b20a07f80c52e41b0d24
Timestamp: 1713964931 Timestamp [UCT]: 2024-04-24 13:22:11 Age [y:d:h:m:s]: 00:259:23:06:09
Block: 1007527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186071 RingCT/type: yes/0
Extra: 013721eef5c4d83668619a03ec1c9cc2c2fa03e74ae4a0b20a07f80c52e41b0d240211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a646a087e6c60d06f5c20b9b3fa1813d3fce9a03448db9960b6528d85438422 0.600000000000 1468893 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": 1007537, "vin": [ { "gen": { "height": 1007527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a646a087e6c60d06f5c20b9b3fa1813d3fce9a03448db9960b6528d85438422" } } ], "extra": [ 1, 55, 33, 238, 245, 196, 216, 54, 104, 97, 154, 3, 236, 28, 156, 194, 194, 250, 3, 231, 74, 228, 160, 178, 10, 7, 248, 12, 82, 228, 27, 13, 36, 2, 17, 0, 0, 0, 1, 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