← previous blocknext block →recent activity
Analyzing
Block #112,255,324
19 transactions · 17 stateful · 2026-10-10 18:35:15 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,255,324 · 19 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
2w03w113w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5989b4…4dbf
0x34b655…2a6f
6 touches
3 conflicts
0xb4656137…5858
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xf421f13f…3106
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x16e21d8b…fa65
0x34b655…2a6f
4 touches
1 conflict
0x25732dfc…aacc
0x34b655…2a6f
4 touches
1 conflict
0x2fde3e82…2035
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 0x1b5989b404…ca4dbf
Audit this contract →
← previous block·next block →recent activity