← previous blocknext block →recent activity
Analyzing
Block #107,839,104
11 transactions · 10 stateful · 2026-09-25 07:57:02 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,839,104 · 11 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
2w03w05w16w27w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd07321…1c31
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x7ec5c72b…4598
0x34b655…2a6f
4 touches
1 conflict
0xe073e79e…b9e8
0x34b655…2a6f
4 touches
1 conflict
0x0b01063c…fd72
0x851145…3f07
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0x950f7d79…3cf2
0x851145…3f07
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
6 conflicts on slot 0xdcd0732149…7d1c31
Audit this contract →
← previous block·next block →recent activity