Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199eab2de744a0fc8a51128b4239c131802df8f83bf29a89c7b61714861e8bf9

Tx prefix hash: b8ade2a5db4eeeb11d6329fce9cca3d61ab9e723ac309e8353cb178d88686590
Tx public key: 2df20dfe171925276b940f32548c2d5d4360dbc6c506fb0ed65b1041e8774c7c
Timestamp: 1755189509 Timestamp [UCT]: 2025-08-14 16:38:29 Age [y:d:h:m:s]: 00:052:08:44:51
Block: 1346768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36913 RingCT/type: yes/0
Extra: 012df20dfe171925276b940f32548c2d5d4360dbc6c506fb0ed65b1041e8774c7c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd76962dca686156f0dbd6fdb8201ac8826cfc50597c39f74fa258e7b036c8f8 0.600000000000 1834673 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": 1346778, "vin": [ { "gen": { "height": 1346768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd76962dca686156f0dbd6fdb8201ac8826cfc50597c39f74fa258e7b036c8f8" } } ], "extra": [ 1, 45, 242, 13, 254, 23, 25, 37, 39, 107, 148, 15, 50, 84, 140, 45, 93, 67, 96, 219, 198, 197, 6, 251, 14, 214, 91, 16, 65, 232, 119, 76, 124, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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