Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5a13083f5404b73c8a5fcff2b3d625576aa26dd2b37cceff3ab987aff82c81

Tx prefix hash: 9a55a72e725ad264fc47cf852bf372add51fd6a1aa87fddec01d013cb58736ca
Tx public key: fa8363032d8d95658478c09bd7781d940dd4fde531ceb51a5fcd278360254e4a
Timestamp: 1772007703 Timestamp [UTC]: 2026-02-25 08:21:43 Age [y:d:h:m:s]: 00:267:02:57:21
Block: 1485400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196444 RingCT/type: yes/0
Extra: 01fa8363032d8d95658478c09bd7781d940dd4fde531ceb51a5fcd278360254e4a02110000000df188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 308a6168b79e578dcdf9a7e5d0188c2c18751467fdeeb66e35d7c2cbee1265e8 0.000600000000 1974834 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": 1485410, "vin": [ { "gen": { "height": 1485400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "308a6168b79e578dcdf9a7e5d0188c2c18751467fdeeb66e35d7c2cbee1265e8" } } ], "extra": [ 1, 250, 131, 99, 3, 45, 141, 149, 101, 132, 120, 192, 155, 215, 120, 29, 148, 13, 212, 253, 229, 49, 206, 181, 26, 95, 205, 39, 131, 96, 37, 78, 74, 2, 17, 0, 0, 0, 13, 241, 136, 200, 168, 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: