Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d021a3cb346f091522c1c1d5ce56061e591adb166210b222bf61931f84b52092

Tx prefix hash: 6dc7118744f561f39bfc38e4f503c7df110eabfaf76089bd9f6ce7b49503b3a2
Tx public key: e02db386f5495dd76be9c9a41a5fca91a5be132174b3e5b4c169ab403fb2779f
Timestamp: 1761487926 Timestamp [UCT]: 2025-10-26 14:12:06 Age [y:d:h:m:s]: 00:032:17:05:09
Block: 1398398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23414 RingCT/type: yes/0
Extra: 01e02db386f5495dd76be9c9a41a5fca91a5be132174b3e5b4c169ab403fb2779f021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d39d61434eddeab514c57973eef0f86414f0f3abfd54f2344a2f24854fc36b1c 0.600000000000 1886697 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": 1398408, "vin": [ { "gen": { "height": 1398398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d39d61434eddeab514c57973eef0f86414f0f3abfd54f2344a2f24854fc36b1c" } } ], "extra": [ 1, 224, 45, 179, 134, 245, 73, 93, 215, 107, 233, 201, 164, 26, 95, 202, 145, 165, 190, 19, 33, 116, 179, 229, 180, 193, 105, 171, 64, 63, 178, 119, 159, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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