← previous blocknext block →recent activity
Analyzing
Block #108,493,983
16 transactions · 16 stateful · 2026-09-27 14:53:00 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,493,983 · 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
5w06w17w18w210w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1729dbeb…60a1
0x34b655…2a6f
4 touches
1 conflict
0x1abfd3ae…2999
0x34b655…2a6f
4 touches
1 conflict
0x26b816a2…89a5
0x34b655…2a6f
4 touches
1 conflict
0x3b8da5cc…e045
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0x1729dbeb1d…2e60a1
Audit this contract →
← previous block·next block →recent activity