← previous blocknext block →recent activity
Analyzing
Block #101,666,345
13 transactions · 13 stateful · 2026-09-03 16:49:04 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,666,345 · 13 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
1w02w16w17w28w311w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d971bc9…fadc
0x34b655…2a6f
6 touches
3 conflicts
0xa9dc84b8…e098
0x34b655…2a6f
6 touches
3 conflicts
0x4a830181…d1df
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0xd139f50e…2bb6
0x34b655…2a6f
6 touches
3 conflicts
0x6713b018…05f3
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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 0x4d971bc9ee…5efadc
Audit this contract →
← previous block·next block →recent activity