Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518fb4554b6ae0c6ff152201dc7102ef43451d82769ff72502b09f082efad856

Tx prefix hash: 70ef7a9497b5a6daf0108d9a3e0d8b48c8a0b9b53c664e732999365968ab257f
Tx public key: e73e6f8a96ca0363ac3e1a1511b723892eb18a050becb4189260d5d6b3208177
Timestamp: 1712645066 Timestamp [UCT]: 2024-04-09 06:44:26 Age [y:d:h:m:s]: 01:001:14:44:20
Block: 996551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262131 RingCT/type: yes/0
Extra: 01e73e6f8a96ca0363ac3e1a1511b723892eb18a050becb4189260d5d6b32081770211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf6aaba6e8bf1ff43e39de95492d56de7c38d48fb86657482bee31d4e3f40ce 0.600000000000 1456973 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": 996561, "vin": [ { "gen": { "height": 996551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf6aaba6e8bf1ff43e39de95492d56de7c38d48fb86657482bee31d4e3f40ce" } } ], "extra": [ 1, 231, 62, 111, 138, 150, 202, 3, 99, 172, 62, 26, 21, 17, 183, 35, 137, 46, 177, 138, 5, 11, 236, 180, 24, 146, 96, 213, 214, 179, 32, 129, 119, 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