Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160fa06622156cdc3df1939f8b369a4d3f9cbc5cdb7da1082165cdb87b9ca87a

Tx prefix hash: f640b3550b6abd3693c90b9a21f43b135096c42a08b4d7921297b57159137216
Tx public key: 031a4d11e370d75144edf340a5e1ba5c529d26ca1d053812e1a336d528cf4c2e
Timestamp: 1643539532 Timestamp [UTC]: 2022-01-30 10:45:32 Age [y:d:h:m:s]: 04:066:00:24:54
Block: 428431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1084864 RingCT/type: yes/0
Extra: 01031a4d11e370d75144edf340a5e1ba5c529d26ca1d053812e1a336d528cf4c2e0211000000024a0f5013000000000000000000

1 output(s) for total of 0.023357725871 xmr

stealth address amount amount idx tag
00: ef7a03a689220c4966ed36d95030df1a4ab64b0963767aef66d2976e3fed3f7a 0.023357725871 837825 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 dinastycoin-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": 428441, "vin": [ { "gen": { "height": 428431 } } ], "vout": [ { "amount": 23357725871, "target": { "key": "ef7a03a689220c4966ed36d95030df1a4ab64b0963767aef66d2976e3fed3f7a" } } ], "extra": [ 1, 3, 26, 77, 17, 227, 112, 215, 81, 68, 237, 243, 64, 165, 225, 186, 92, 82, 157, 38, 202, 29, 5, 56, 18, 225, 163, 54, 213, 40, 207, 76, 46, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369