← previous blocknext block →recent activity
Analyzing
Block #101,802,434
10 transactions · 10 stateful · 2026-09-04 04:13:34 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,802,434 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0x3efc4ea8…a302
0x34b655…2a6f
4 touches
1 conflict
0x6324ccc9…14fd
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0x09f6001c…4da3
0x34b655…2a6f
2 touches
0 conflicts
0x2741e3b9…944b
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 0x4abfb3894a…c318f4
Audit this contract →
← previous block·next block →recent activity