Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 813ae3fb128d68c35768a309da89d6ed4626adcd2ae3a883c8227424307f41d6

Tx prefix hash: 0e53006c82d6b8a3fd0b575be972d395b797f0a0e286d92d7353283a682e3f1b
Tx public key: e2907d67e3b730388884322939e84cc3ce270b1a01c7e08d05b45f608e174fe9
Timestamp: 1720805159 Timestamp [UCT]: 2024-07-12 17:25:59 Age [y:d:h:m:s]: 00:294:01:16:32
Block: 1064241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210095 RingCT/type: yes/0
Extra: 01e2907d67e3b730388884322939e84cc3ce270b1a01c7e08d05b45f608e174fe902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73f6fe62414338d3d8206b9a2018ec04c351921b159d92b96c0e5334dac7769d 0.600000000000 1534764 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": 1064251, "vin": [ { "gen": { "height": 1064241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73f6fe62414338d3d8206b9a2018ec04c351921b159d92b96c0e5334dac7769d" } } ], "extra": [ 1, 226, 144, 125, 103, 227, 183, 48, 56, 136, 132, 50, 41, 57, 232, 76, 195, 206, 39, 11, 26, 1, 199, 224, 141, 5, 180, 95, 96, 142, 23, 79, 233, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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