← previous blocknext block →recent activity
Analyzing
Block #112,343,095
16 transactions · 15 stateful · 2026-10-11 01:56:50 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,343,095 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc746aff6…908d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe0542e18…561a
0x34b655…2a6f
4 touches
1 conflict
0x0274d321…9b62
0x34b655…2a6f
4 touches
1 conflict
0x3b7f451f…dcf6
0x34b655…2a6f
4 touches
1 conflict
0x8a57acfa…1171
0x34b655…2a6f
4 touches
1 conflict
0xdc686ec4…237e
0x30a88b…7102
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity