← previous blocknext block →recent activity
Analyzing
Block #108,619,857
15 transactions · 15 stateful · 2026-09-28 01:26:51 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,619,857 · 15 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
1w02w03w16w17w28w110w211w312w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ff9db2e…22f6
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x73c2c831…6d2c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xce71855e…b8b4
0x34b655…2a6f
6 touches
3 conflicts
0xc67fef76…f519
0x34b655…2a6f
5 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0x920a7694…3284
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 0x3ff9db2e2d…9122f6
Audit this contract →
← previous block·next block →recent activity