← previous blocknext block →recent activity
Analyzing
Block #102,271,112
24 transactions · 22 stateful · 2026-09-05 19:45:59 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,271,112 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w110w012w117w118w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x3c67d31e…3dbe
0x34b655…2a6f
4 touches
1 conflict
0x3d408a46…8a53
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x5dccf775…6d6a
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity