← previous blocknext block →recent activity
Analyzing
Block #108,630,472
16 transactions · 13 stateful · 2026-09-28 02:20:18 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,630,472 · 16 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
2w03w16w010w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0xcfb4bc03…997d
0x34b655…2a6f
4 touches
1 conflict
0xa8659d3c…ce52
0x34b655…2a6f
4 touches
1 conflict
0xac6018d0…517f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x06d6349e…686d
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
1 conflict on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity