Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034860b134a8ba793b639dcc49ced5a11b7b10e3b6652229a97664350841f14f

Tx prefix hash: de4ddfa30af832faa37f52b5b6b15dc730c29c28cea83ae114daa8f4f2b744bd
Tx public key: f4bf0688967f28f41ddd08505b632f6b46d680c538932c0440922d46852c49d3
Timestamp: 1625408366 Timestamp [UCT]: 2021-07-04 14:19:26 Age [y:d:h:m:s]: 03:287:06:06:51
Block: 288178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 974766 RingCT/type: yes/0
Extra: 01f4bf0688967f28f41ddd08505b632f6b46d680c538932c0440922d46852c49d302110000000214aef7b9000000000000000000

1 output(s) for total of 68.101188366000 dcy

stealth address amount amount idx
00: 30d45476d74fbe5b933b5d300c436f3d7b411f4cb1a5e14dd5b32507bf829e11 68.101188366000 603801 of 0

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": 288188, "vin": [ { "gen": { "height": 288178 } } ], "vout": [ { "amount": 68101188366, "target": { "key": "30d45476d74fbe5b933b5d300c436f3d7b411f4cb1a5e14dd5b32507bf829e11" } } ], "extra": [ 1, 244, 191, 6, 136, 150, 127, 40, 244, 29, 221, 8, 80, 91, 99, 47, 107, 70, 214, 128, 197, 56, 147, 44, 4, 64, 146, 45, 70, 133, 44, 73, 211, 2, 17, 0, 0, 0, 2, 20, 174, 247, 185, 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