Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f68bb07d8717d8903dae4b26c30f92483fd73e9f74a650a9963a5595404eaa

Tx prefix hash: 5a2224989ff016aba18b815b0c5e2959a3380e246e72dc484c386341780f0cc9
Tx public key: 243374e9d1e2a27013fe8ce82d3f095c18f28599ed282ae8306dbc7b02526280
Timestamp: 1707298196 Timestamp [UCT]: 2024-02-07 09:29:56 Age [y:d:h:m:s]: 01:108:11:27:42
Block: 952240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338627 RingCT/type: yes/0
Extra: 01243374e9d1e2a27013fe8ce82d3f095c18f28599ed282ae8306dbc7b025262800211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b469c713a7d062808a7734de5a7e961b2b21081b0788f662202086e67d8d6b90 0.600000000000 1411136 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": 952250, "vin": [ { "gen": { "height": 952240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b469c713a7d062808a7734de5a7e961b2b21081b0788f662202086e67d8d6b90" } } ], "extra": [ 1, 36, 51, 116, 233, 209, 226, 162, 112, 19, 254, 140, 232, 45, 63, 9, 92, 24, 242, 133, 153, 237, 40, 42, 232, 48, 109, 188, 123, 2, 82, 98, 128, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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