← previous blocknext block →recent activity
Analyzing
Block #102,210,643
28 transactions · 28 stateful · 2026-09-05 14:39:39 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,210,643 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w118w019w121w223w024w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x15e46d60…7be8
0x34b655…2a6f
4 touches
1 conflict
0x3b25d07f…1dee
0x34b655…2a6f
4 touches
1 conflict
0x3e93b8a2…4615
0x34b655…2a6f
4 touches
1 conflict
0x44f26cbe…58c2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity