Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdff1740e14a2ce81755708695f604ee8769ca7ba5abeefa0ad4de7f7fcc1595

Tx prefix hash: 8847ea3443cc8d9661dfbf33d792c31e27031c9a041fabf5f14427c2ebeddc73
Tx public key: dd6b2ba23cf9372efad92ae809daf28984a79c5de6e8c55f45196bf388f93304
Timestamp: 1757744915 Timestamp [UTC]: 2025-09-13 06:28:35 Age [y:d:h:m:s]: 01:068:05:38:24
Block: 1367365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315308 RingCT/type: yes/0
Extra: 01dd6b2ba23cf9372efad92ae809daf28984a79c5de6e8c55f45196bf388f93304021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 85b26a8e711b94d29b10f51f692b4f695153efbbf5f122804ba44b2cb7051cf0 0.000600000000 1855404 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": 1367375, "vin": [ { "gen": { "height": 1367365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85b26a8e711b94d29b10f51f692b4f695153efbbf5f122804ba44b2cb7051cf0" } } ], "extra": [ 1, 221, 107, 43, 162, 60, 249, 55, 46, 250, 217, 42, 232, 9, 218, 242, 137, 132, 167, 156, 93, 230, 232, 197, 95, 69, 25, 107, 243, 136, 249, 51, 4, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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: