Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c682b2c97404e548136b3e3a0b81eec9184b6a549499b3bcc16cd20db3fcd8

Tx prefix hash: 0be87dc24d725a668ecd5af2af0e55cdd20966baa3008ebe5acd6dfecd363d3d
Tx public key: 3f00c4ac51429ba894ec136223030fd3e33bb23fa3f7e5b1d3d035f93b8a0932
Timestamp: 1645816160 Timestamp [UTC]: 2022-02-25 19:09:20 Age [y:d:h:m:s]: 04:267:09:30:20
Block: 446392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1235246 RingCT/type: yes/0
Extra: 013f00c4ac51429ba894ec136223030fd3e33bb23fa3f7e5b1d3d035f93b8a0932021100000019c9067537000000000000000000

1 output(s) for total of 0.020366588182 xmr

stealth address amount amount idx tag
00: 558be52803c206a30641ae992fd77dea31bc6dca3fde592cc071801f8a3151e4 0.020366588182 860269 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": 446402, "vin": [ { "gen": { "height": 446392 } } ], "vout": [ { "amount": 20366588182, "target": { "key": "558be52803c206a30641ae992fd77dea31bc6dca3fde592cc071801f8a3151e4" } } ], "extra": [ 1, 63, 0, 196, 172, 81, 66, 155, 168, 148, 236, 19, 98, 35, 3, 15, 211, 227, 59, 178, 63, 163, 247, 229, 177, 211, 208, 53, 249, 59, 138, 9, 50, 2, 17, 0, 0, 0, 25, 201, 6, 117, 55, 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: