← previous blocknext block →recent activity
Analyzing
Block #102,419,485
14 transactions · 14 stateful · 2026-09-06 08:17:42 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,419,485 · 14 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
6w09w110w211w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde07eb52…8ae5
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3c67d31e…3dbe
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x941bd594…21fd
0x34b655…2a6f
4 touches
1 conflict
0x75dd818d…df4c
0x34b655…2a6f
3 touches
1 conflict
0x21e79ad8…c5db
0x34b655…2a6f
2 touches
0 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 0xde07eb525e…2b8ae5
Audit this contract →
← previous block·next block →recent activity