Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760bd83e5062c180afb899c016e34ef75ad7434b9cdc6cbf3885fa05bbf218bf

Tx prefix hash: 445963fcb94a8660768d2e6e83d586bdcfc26907b513e1a8a2c21815a3c49804
Tx public key: 0acd5de6321720e496bd3bc56041ffd0967abbaaa30b4ff0ea95bd9c86a4aed4
Timestamp: 1712793684 Timestamp [UTC]: 2024-04-11 00:01:24 Age [y:d:h:m:s]: 02:028:22:05:07
Block: 997784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532860 RingCT/type: yes/0
Extra: 010acd5de6321720e496bd3bc56041ffd0967abbaaa30b4ff0ea95bd9c86a4aed40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 43dc82932a12d98aaa16d48f5d1c093f96b35f25e26ad9facd40f8018d129bd8 0.000600000000 1458218 of 15 -

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": 997794, "vin": [ { "gen": { "height": 997784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43dc82932a12d98aaa16d48f5d1c093f96b35f25e26ad9facd40f8018d129bd8" } } ], "extra": [ 1, 10, 205, 93, 230, 50, 23, 32, 228, 150, 189, 59, 197, 96, 65, 255, 208, 150, 122, 187, 170, 163, 11, 79, 240, 234, 149, 189, 156, 134, 164, 174, 212, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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: