Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebc3933afb2eda749b5268806cd46d80dcf89d304916807b6f72677f46397b35

Tx prefix hash: a41eb4e35f04b1fe381769c7022c013ee6f707f7d245fe12d09e3496463996fe
Tx public key: 364960b0265e8ee4c7c0b8c7afaeaf37e7890f4bb4e22b04848d8feb7a4abde6
Timestamp: 1663368332 Timestamp [UTC]: 2022-09-16 22:45:32 Age [y:d:h:m:s]: 04:067:13:16:00
Block: 589471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1094023 RingCT/type: yes/0
Extra: 01364960b0265e8ee4c7c0b8c7afaeaf37e7890f4bb4e22b04848d8feb7a4abde602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.006836565061 xmr

stealth address amount amount idx tag
00: 2151155d2d526f01dd956666c1e75eee3ad8d17870851fbaf5e47805ec17a6c5 0.006836565061 1023784 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": 589481, "vin": [ { "gen": { "height": 589471 } } ], "vout": [ { "amount": 6836565061, "target": { "key": "2151155d2d526f01dd956666c1e75eee3ad8d17870851fbaf5e47805ec17a6c5" } } ], "extra": [ 1, 54, 73, 96, 176, 38, 94, 142, 228, 199, 192, 184, 199, 175, 174, 175, 55, 231, 137, 15, 75, 180, 226, 43, 4, 132, 141, 143, 235, 122, 74, 189, 230, 2, 17, 0, 0, 0, 2, 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: