Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389fd9b5b5e3730283fafe2e2c085d32b76416c77fe31adb38f2c9996430eda3

Tx prefix hash: 77dd6631dbb266626b59e00de90638e8f45b2c5e9162054cae3ee84927ac56a6
Tx public key: de69e9d1d000bc1366aa88a98b9e0323d42b2496e1e7c5bde3a2238b6f187aaa
Timestamp: 1767293037 Timestamp [UTC]: 2026-01-01 18:43:57 Age [y:d:h:m:s]: 00:045:15:01:14
Block: 1446499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 32463 RingCT/type: yes/0
Extra: 01de69e9d1d000bc1366aa88a98b9e0323d42b2496e1e7c5bde3a2238b6f187aaa020900000004f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd736fc4fb9003b46126e23c4eabf69c9ef3a5669798a710a72ba6c07790689e 0.000600000000 1935451 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": 1446509, "vin": [ { "gen": { "height": 1446499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd736fc4fb9003b46126e23c4eabf69c9ef3a5669798a710a72ba6c07790689e" } } ], "extra": [ 1, 222, 105, 233, 209, 208, 0, 188, 19, 102, 170, 136, 169, 139, 158, 3, 35, 212, 43, 36, 150, 225, 231, 197, 189, 227, 162, 35, 139, 111, 24, 122, 170, 2, 9, 0, 0, 0, 4, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369