Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddfe7dc2c6e2be7e6e5d554e827e2a7c68f824cb44b7cfd74bbd79e81a33bfd7

Tx prefix hash: 4ac6e0dafb756c3399c8adf827cf93702310823cd0d0e936a23de2996984cb2e
Tx public key: 5f844e695d7c7d66caf32c68ba4507646371d3c4375a6d317f2f7ee26d3bdcf3
Timestamp: 1757151687 Timestamp [UTC]: 2025-09-06 09:41:27 Age [y:d:h:m:s]: 01:070:06:05:55
Block: 1362540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316458 RingCT/type: yes/0
Extra: 015f844e695d7c7d66caf32c68ba4507646371d3c4375a6d317f2f7ee26d3bdcf3021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a11721360e6b31da5e2f3c0461a3b2a37878506f0067bf2c442ddcefb8bef60e 0.000600000000 1850571 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": 1362550, "vin": [ { "gen": { "height": 1362540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a11721360e6b31da5e2f3c0461a3b2a37878506f0067bf2c442ddcefb8bef60e" } } ], "extra": [ 1, 95, 132, 78, 105, 93, 124, 125, 102, 202, 243, 44, 104, 186, 69, 7, 100, 99, 113, 211, 196, 55, 90, 109, 49, 127, 47, 126, 226, 109, 59, 220, 243, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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: