← previous blocknext block →recent activity
Analyzing
Block #108,402,442
23 transactions · 16 stateful · 2026-09-27 07:12:13 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,402,442 · 23 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
1w04w05w16w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0002
0x63e48b…53f2
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity