← previous blocknext block →recent activity
Analyzing
Block #112,350,514
17 transactions · 15 stateful · 2026-10-11 02:34:10 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,350,514 · 17 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
5w06w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a57acfa…1171
0x34b655…2a6f
4 touches
1 conflict
0xe78af6d2…c716
0x34b655…2a6f
4 touches
1 conflict
0x000bba3b…a309
0x34b655…2a6f
4 touches
1 conflict
0x975c3fff…1b37
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x5961f9aa…5fe2
0x34b655…2a6f
4 touches
1 conflict
0x2ac4cf3c…ec38
0x34b655…2a6f
2 touches
0 conflicts
0x8b9e2423…f70f
0x34b655…2a6f
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 0x8a57acfa6a…c81171
Audit this contract →
← previous block·next block →recent activity