← previous blocknext block →recent activity
Analyzing
Block #102,006,991
13 transactions · 13 stateful · 2026-09-04 21:27:28 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,006,991 · 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
2w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x1bfd6618…7d78
0x34b655…2a6f
4 touches
1 conflict
0xa078236e…5e0b
0x34b655…2a6f
4 touches
1 conflict
0xa7481e1f…531f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x00500a94…20d5
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 0x5d1ac445db…e05233
Audit this contract →
← previous block·next block →recent activity