Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398ccc6a8b18d894a7cced291c4fd60f6fb42949cccd70cdc9e2eab7361f688e

Tx prefix hash: 43470bf4447d908d9cac5e2838c6cfc682fb4dc8b444014c33700c9c7b6ec8ff
Tx public key: fe6e2e32912e34a221a2c4c585bd9bfe8e12a327feefe09e9679b62cad85c572
Timestamp: 1726398666 Timestamp [UCT]: 2024-09-15 11:11:06 Age [y:d:h:m:s]: 00:251:02:24:21
Block: 1110603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179329 RingCT/type: yes/0
Extra: 01fe6e2e32912e34a221a2c4c585bd9bfe8e12a327feefe09e9679b62cad85c572021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166190211b216332c375a6e92b59022f3d4e2b35c5b3a08fb451051cf46fede7 0.600000000000 1589266 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": 1110613, "vin": [ { "gen": { "height": 1110603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166190211b216332c375a6e92b59022f3d4e2b35c5b3a08fb451051cf46fede7" } } ], "extra": [ 1, 254, 110, 46, 50, 145, 46, 52, 162, 33, 162, 196, 197, 133, 189, 155, 254, 142, 18, 163, 39, 254, 239, 224, 158, 150, 121, 182, 44, 173, 133, 197, 114, 2, 17, 0, 0, 0, 4, 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