← previous blocknext block →recent activity
Analyzing
Block #102,247,368
22 transactions · 20 stateful · 2026-09-05 17:45:40 UTC
Parallelism
82/100
Blocked
55%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,247,368 · 22 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
2w03w14w25w06w17w211w012w113w014w115w216w318w219w321w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e3635d0…d3ca
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6b267bdf…b173
0x34b655…2a6f
6 touches
3 conflicts
0xa8cebbac…9e8c
0x34b655…2a6f
6 touches
3 conflicts
0xad79410b…96a5
0x34b655…2a6f
6 touches
3 conflicts
0xb82f494f…db33
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x9e3635d014…0bd3ca
Audit this contract →
← previous block·next block →recent activity