Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93d63991da8a20aabee69e87ab0c955d8a85889de1c237ece9d381704dee2f18

Tx prefix hash: f477d628aa157f4e4e2d394e52b9a23dede1852d9178a0cc4169f1550c9c5be0
Tx public key: e5bb914ba6882883a608fd638aefacb076225a32edc7bda3b848086a9f5e4cc0
Timestamp: 1638722004 Timestamp [UTC]: 2021-12-05 16:33:24 Age [y:d:h:m:s]: 04:348:17:48:49
Block: 389057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1292007 RingCT/type: yes/0
Extra: 01e5bb914ba6882883a608fd638aefacb076225a32edc7bda3b848086a9f5e4cc0021100000018e9564d6f000000000000000000

1 output(s) for total of 0.031542275539 xmr

stealth address amount amount idx tag
00: a18b035a23c6d83d5d821ae7a2e62ff2bfd4c03382c0b68862e8aac86bddf1d8 0.031542275539 784034 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": 389067, "vin": [ { "gen": { "height": 389057 } } ], "vout": [ { "amount": 31542275539, "target": { "key": "a18b035a23c6d83d5d821ae7a2e62ff2bfd4c03382c0b68862e8aac86bddf1d8" } } ], "extra": [ 1, 229, 187, 145, 75, 166, 136, 40, 131, 166, 8, 253, 99, 138, 239, 172, 176, 118, 34, 90, 50, 237, 199, 189, 163, 184, 72, 8, 106, 159, 94, 76, 192, 2, 17, 0, 0, 0, 24, 233, 86, 77, 111, 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: