Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 407959436f036c43bb0ff8c8d726275fff7e2c1cc9711cf17d3d3a94e5f670c1

Tx prefix hash: 0532cb3febcbbcd3ce0be0f926ac57828df07d722a012b17f6a957ea4862d050
Tx public key: 3e5731e83af8c7597a805b4c5fee5f5bd4e278f550b39cbcfc74814b45f0edef
Timestamp: 1656863169 Timestamp [UTC]: 2022-07-03 15:46:09 Age [y:d:h:m:s]: 03:320:23:52:48
Block: 535841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1002507 RingCT/type: yes/0
Extra: 013e5731e83af8c7597a805b4c5fee5f5bd4e278f550b39cbcfc74814b45f0edef02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.010292869863 xmr

stealth address amount amount idx tag
00: 588a2d96d09d5d56eb917b76d3ae8116d4cdddccbfdcd29a88bf23d8106d51f0 0.010292869863 965506 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": 535851, "vin": [ { "gen": { "height": 535841 } } ], "vout": [ { "amount": 10292869863, "target": { "key": "588a2d96d09d5d56eb917b76d3ae8116d4cdddccbfdcd29a88bf23d8106d51f0" } } ], "extra": [ 1, 62, 87, 49, 232, 58, 248, 199, 89, 122, 128, 91, 76, 95, 238, 95, 91, 212, 226, 120, 245, 80, 179, 156, 188, 252, 116, 129, 75, 69, 240, 237, 239, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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) | monero version: