Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ed6039e05650f2108c8bb32865c44ed98a68efed2952bd4ec67af7696384ae

Tx prefix hash: 4094fb4c8901369c07e8185964daf93c2358726c8e45d0b54631d70b1cc2edf8
Tx public key: 494b704924d8d7ba75b9e0d5551ff4815dbf83706981e15e0ed2bd8f220a084f
Timestamp: 1731176140 Timestamp [UTC]: 2024-11-09 18:15:40 Age [y:d:h:m:s]: 02:012:03:42:37
Block: 1150126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533368 RingCT/type: yes/0
Extra: 01494b704924d8d7ba75b9e0d5551ff4815dbf83706981e15e0ed2bd8f220a084f021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bfd6feefb55fca64e1920a69550c685ef14f205b66754691e6dc80f5c0eeb0db 0.000600000000 1635343 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": 1150136, "vin": [ { "gen": { "height": 1150126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd6feefb55fca64e1920a69550c685ef14f205b66754691e6dc80f5c0eeb0db" } } ], "extra": [ 1, 73, 75, 112, 73, 36, 216, 215, 186, 117, 185, 224, 213, 85, 31, 244, 129, 93, 191, 131, 112, 105, 129, 225, 94, 14, 210, 189, 143, 34, 10, 8, 79, 2, 17, 0, 0, 0, 1, 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: