← previous blocknext block →recent activity
Analyzing
Block #106,308,249
14 transactions · 14 stateful · 2026-09-19 23:28:26 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,308,249 · 14 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
1w02w13w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81878590…6d25
0x34b655…2a6f
6 touches
3 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x86e46e2e…6119
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
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 0x8187859010…726d25
Audit this contract →
← previous block·next block →recent activity