Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eadd8a34d4f33074a8a4de3ff4a8c34b56933cd116cad36f06ead92abd7e881

Tx prefix hash: 63edc7e6acc558909651a5efd7adb2862e6819ef0e3f6fdf25bad030cc063b9a
Tx public key: 386c5bd2d6594c5d0879e89cd8837134ffa7e8ad4eefc1a5a7d15abc008ffdf2
Timestamp: 1731387229 Timestamp [UTC]: 2024-11-12 04:53:49 Age [y:d:h:m:s]: 02:008:05:59:43
Block: 1151865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530764 RingCT/type: yes/0
Extra: 01386c5bd2d6594c5d0879e89cd8837134ffa7e8ad4eefc1a5a7d15abc008ffdf2021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5c0b24ecaae8d38f177801531e005a799abc843f9d23bc5d82cd0ae631654cfc 0.000600000000 1637448 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": 1151875, "vin": [ { "gen": { "height": 1151865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0b24ecaae8d38f177801531e005a799abc843f9d23bc5d82cd0ae631654cfc" } } ], "extra": [ 1, 56, 108, 91, 210, 214, 89, 76, 93, 8, 121, 232, 156, 216, 131, 113, 52, 255, 167, 232, 173, 78, 239, 193, 165, 167, 209, 90, 188, 0, 143, 253, 242, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: