← previous blocknext block →recent activity
Analyzing
Block #101,668,486
15 transactions · 14 stateful · 2026-09-03 16:59:50 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,668,486 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee799cea…1f1c
0x34b655…2a6f
4 touches
1 conflict
0xc7345139…71df
0x34b655…2a6f
4 touches
1 conflict
0xc7bb912f…ad41
0x34b655…2a6f
4 touches
1 conflict
0xc9ca92b3…ac3f
0x34b655…2a6f
4 touches
1 conflict
0xd4f6a526…ad10
0x34b655…2a6f
4 touches
1 conflict
0xeb4304a5…dd06
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
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
1 conflict on slot 0xee799ceaa4…2f1f1c
Audit this contract →
← previous block·next block →recent activity