Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d6511cdfdb34e1aa01ca556e0bfa7a9f8a10bc04120dd5bfdff2c7b26f94d2

Tx prefix hash: a44ab478a584df140fb6ad791882122d1e79b7a35110b98bd47bf2ce98974afd
Tx public key: d00f896ed7e0cda82de27905eae4cf4bbae7d014684f47e86b241aab7cccb8b0
Timestamp: 1736517854 Timestamp [UCT]: 2025-01-10 14:04:14 Age [y:d:h:m:s]: 00:156:20:33:39
Block: 1194352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111818 RingCT/type: yes/0
Extra: 01d00f896ed7e0cda82de27905eae4cf4bbae7d014684f47e86b241aab7cccb8b00211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4caa69db50ef87023e23a49585466e6d2318fdc48df878342a087da869a6595 0.600000000000 1680921 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": 1194362, "vin": [ { "gen": { "height": 1194352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4caa69db50ef87023e23a49585466e6d2318fdc48df878342a087da869a6595" } } ], "extra": [ 1, 208, 15, 137, 110, 215, 224, 205, 168, 45, 226, 121, 5, 234, 228, 207, 75, 186, 231, 208, 20, 104, 79, 71, 232, 107, 36, 26, 171, 124, 204, 184, 176, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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