← previous blocknext block →recent activity
Analyzing
Block #101,800,870
8 transactions · 8 stateful · 2026-09-04 04:05:42 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,800,870 · 8 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
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9013e1ee…8e2c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x2e42c10e…ac60
0x34b655…2a6f
2 touches
0 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
0x50e131b5…e277
0x34b655…2a6f
2 touches
0 conflicts
0x56354702…7ee7
0x34b655…2a6f
2 touches
0 conflicts
0x69630499…76d1
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 0x9013e1ee1a…c48e2c
Audit this contract →
← previous block·next block →recent activity