Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 005c607683a3e97d6983936b70016d352ce5b9c65023568ed2435ded24dbe3ac

Tx prefix hash: a3e9a1cbce7485b7a77e4cc4b0cbde3a1e873eb2e40d5a8fbd8934a6c0d17a80
Tx public key: 4d938689d93e1de735a2f545a94e032f1b01d18c3eecc96edb956b182805d9aa
Timestamp: 1714066050 Timestamp [UCT]: 2024-04-25 17:27:30 Age [y:d:h:m:s]: 00:245:22:14:03
Block: 1008351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176033 RingCT/type: yes/0
Extra: 014d938689d93e1de735a2f545a94e032f1b01d18c3eecc96edb956b182805d9aa0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129649c7051a63b3f3fa42b6af338f54bab15f350ddc78993b8cc7f2c044f763 0.600000000000 1469821 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": 1008361, "vin": [ { "gen": { "height": 1008351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129649c7051a63b3f3fa42b6af338f54bab15f350ddc78993b8cc7f2c044f763" } } ], "extra": [ 1, 77, 147, 134, 137, 217, 62, 29, 231, 53, 162, 245, 69, 169, 78, 3, 47, 27, 1, 209, 140, 62, 236, 201, 110, 219, 149, 107, 24, 40, 5, 217, 170, 2, 17, 0, 0, 0, 2, 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