← previous blocknext block →recent activity
Analyzing
Block #112,612,615
21 transactions · 20 stateful · 2026-10-12 00:32:52 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,612,615 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w010w114w116w217w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b2e6393…108b
0x34b655…2a6f
6 touches
3 conflicts
0x708d7a74…09e3
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x1b458e47…5ab5
0x34b655…2a6f
4 touches
1 conflict
0x2d0a3181…203d
0x34b655…2a6f
4 touches
1 conflict
0x3a00de10…175c
0x34b655…2a6f
4 touches
1 conflict
0x4f757b4e…016e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x0b2e639379…c8108b
Audit this contract →
← previous block·next block →recent activity