Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac96276eaeb496708dda53968068371db53792e8a4e35fd08f01012cfa7702f2

Tx prefix hash: d2008b725d182ae22476a8d1639bd78308edbe5731deb886c82938f1a05dfbdc
Tx public key: 563440c70a910c0f6bc7191f2b32f95befbcb84d4f339a99c7ae2e80ad063ba7
Timestamp: 1699832929 Timestamp [UTC]: 2023-11-12 23:48:49 Age [y:d:h:m:s]: 03:009:06:49:34
Block: 890369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 792864 RingCT/type: yes/0
Extra: 01563440c70a910c0f6bc7191f2b32f95befbcb84d4f339a99c7ae2e80ad063ba702110000000afaf35c9c000000000000000000

1 output(s) for total of 0.000688395291 xmr

stealth address amount amount idx tag
00: 65226ffa6055d4f68a5501b49a7a8e6d4fa99fb4b9e25bef31fb92c5d82d801d 0.000688395291 1346392 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": 890379, "vin": [ { "gen": { "height": 890369 } } ], "vout": [ { "amount": 688395291, "target": { "key": "65226ffa6055d4f68a5501b49a7a8e6d4fa99fb4b9e25bef31fb92c5d82d801d" } } ], "extra": [ 1, 86, 52, 64, 199, 10, 145, 12, 15, 107, 199, 25, 31, 43, 50, 249, 91, 239, 188, 184, 77, 79, 51, 154, 153, 199, 174, 46, 128, 173, 6, 59, 167, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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: