Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c57d3416d7c1c74980464d495abce193df53ec9c66c632e9496e6e4f9c9c1507

Tx prefix hash: f3e53b432dd848e3a5365abe130256d34063de6a7a9bdfa2f3f1d6a11eed899a
Tx public key: fffa3f64db3687b299c4ef89bc7c45e997c47c2d1a37011191aa4d524405d636
Timestamp: 1713794230 Timestamp [UCT]: 2024-04-22 13:57:10 Age [y:d:h:m:s]: 01:192:06:59:17
Block: 1006108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396072 RingCT/type: yes/0
Extra: 01fffa3f64db3687b299c4ef89bc7c45e997c47c2d1a37011191aa4d524405d63602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f6f0e5a8b9401be5a3c256203604784c1b79162bc8fc4f54305700bece0ab7 0.600000000000 1467030 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": 1006118, "vin": [ { "gen": { "height": 1006108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f6f0e5a8b9401be5a3c256203604784c1b79162bc8fc4f54305700bece0ab7" } } ], "extra": [ 1, 255, 250, 63, 100, 219, 54, 135, 178, 153, 196, 239, 137, 188, 124, 69, 233, 151, 196, 124, 45, 26, 55, 1, 17, 145, 170, 77, 82, 68, 5, 214, 54, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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