Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3836847647b755659bfdb81fb18d01672efaaae328bfe728fdc3b0a7d3919d3e

Tx prefix hash: cc9212d00cf9630b3bd3f9e36a99e5822ce5936ac499a3eecf5d1491befe8f36
Tx public key: 7d9adbdc68fb1a8d5f7d72795d91798bbe59844570d862ef780150f00a7fc7c0
Timestamp: 1743213479 Timestamp [UTC]: 2025-03-29 01:57:59 Age [y:d:h:m:s]: 01:051:04:42:05
Block: 1249517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288552 RingCT/type: yes/0
Extra: 017d9adbdc68fb1a8d5f7d72795d91798bbe59844570d862ef780150f00a7fc7c00211000000069ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0bef7ad01d1654ffbb6d2bb5ed4e6204343b41a2972f5d795990265500bd4215 0.000600000000 1736556 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": 1249527, "vin": [ { "gen": { "height": 1249517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bef7ad01d1654ffbb6d2bb5ed4e6204343b41a2972f5d795990265500bd4215" } } ], "extra": [ 1, 125, 154, 219, 220, 104, 251, 26, 141, 95, 125, 114, 121, 93, 145, 121, 139, 190, 89, 132, 69, 112, 216, 98, 239, 120, 1, 80, 240, 10, 127, 199, 192, 2, 17, 0, 0, 0, 6, 155, 166, 41, 223, 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: