← previous blocknext block →recent activity
Analyzing
Block #108,447,902
14 transactions · 10 stateful · 2026-09-27 11:01:02 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,447,902 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518b8dce…6d60
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf137ef00…8f90
0x34b655…2a6f
4 touches
1 conflict
0x235bbb77…89ea
0x34b655…2a6f
4 touches
1 conflict
0x37f93b32…cc57
0x34b655…2a6f
4 touches
1 conflict
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x027fc5ff…5db2
0x6657d1…8ccc
2 touches
0 conflicts
0x0eb23f4c…dc84
0x6657d1…8ccc
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
1 conflict on slot 0x518b8dce2e…7e6d60
Audit this contract →
← previous block·next block →recent activity