Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03c157e834d75a992911036100e404079caa96733d75bf79a2cef6c3ceaa3b38

Tx prefix hash: 09dfe8c9d60aa69474041dcf4311510f018847dd340fbdcc45f62dabba1c8a88
Tx public key: 089b363292c6209f731e1b8f387fc7826a01c7c8b80244037ecc3f7e41cea6b3
Timestamp: 1714182569 Timestamp [UCT]: 2024-04-27 01:49:29 Age [y:d:h:m:s]: 01:192:18:37:45
Block: 1009315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396416 RingCT/type: yes/0
Extra: 01089b363292c6209f731e1b8f387fc7826a01c7c8b80244037ecc3f7e41cea6b30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eae9da3d81b13e7c31af183348d0a4ae1e7b35623e154dd35bd5c680ac0d66e1 0.600000000000 1470953 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": 1009325, "vin": [ { "gen": { "height": 1009315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eae9da3d81b13e7c31af183348d0a4ae1e7b35623e154dd35bd5c680ac0d66e1" } } ], "extra": [ 1, 8, 155, 54, 50, 146, 198, 32, 159, 115, 30, 27, 143, 56, 127, 199, 130, 106, 1, 199, 200, 184, 2, 68, 3, 126, 204, 63, 126, 65, 206, 166, 179, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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