← previous blocknext block →recent activity
Analyzing
Block #102,006,966
17 transactions · 17 stateful · 2026-09-04 21:27:20 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,006,966 · 17 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
2w03w110w011w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0f6895c…e428
0x34b655…2a6f
4 touches
1 conflict
0xf5d28bce…c32c
0x34b655…2a6f
4 touches
1 conflict
0xfcd7574f…a3a2
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
0x6974210b…154c
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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 0xc0f6895c5d…fee428
Audit this contract →
← previous block·next block →recent activity