Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2117890112bbed83205da31afcb1acd41afae108404148dbabad0deba33cee8

Tx prefix hash: c9b3382793c3401a940dfe65f7b0d9bbde4d0d24fc5f50329c2e795ca3c1751f
Tx public key: 9ee8e93c4720fbbbaf7fa1a3e1566181b4380bc3b42cff7dc752582bb2d89ecc
Timestamp: 1764808833 Timestamp [UCT]: 2025-12-04 00:40:33 Age [y:d:h:m:s]: 00:001:11:17:42
Block: 1425911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1064 RingCT/type: yes/0
Extra: 019ee8e93c4720fbbbaf7fa1a3e1566181b4380bc3b42cff7dc752582bb2d89ecc021100000013d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4e44a1b2962bdcdcb3b6e1cad09e5de2a3cb6bfa97ce3a9a365abe00d72bf94 0.600000000000 1914594 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": 1425921, "vin": [ { "gen": { "height": 1425911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4e44a1b2962bdcdcb3b6e1cad09e5de2a3cb6bfa97ce3a9a365abe00d72bf94" } } ], "extra": [ 1, 158, 232, 233, 60, 71, 32, 251, 187, 175, 127, 161, 163, 225, 86, 97, 129, 180, 56, 11, 195, 180, 44, 255, 125, 199, 82, 88, 43, 178, 216, 158, 204, 2, 17, 0, 0, 0, 19, 214, 225, 157, 124, 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