← previous blocknext block →recent activity
Analyzing
Block #102,056,375
16 transactions · 16 stateful · 2026-09-05 01:37:29 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,056,375 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w09w110w211w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17390c78…bf0c
0x34b655…2a6f
6 touches
3 conflicts
0x25ec781a…dca9
0x34b655…2a6f
4 touches
1 conflict
0x31f6e455…1aca
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
3 conflicts on slot 0x17390c7851…6bbf0c
Audit this contract →
← previous block·next block →recent activity