← previous blocknext block →recent activity
Analyzing
Block #106,273,695
12 transactions · 12 stateful · 2026-09-19 20:34:34 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,273,695 · 12 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
1w02w03w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x19d9bbc3…65b5
0x34b655…2a6f
4 touches
1 conflict
0x0f110884…dd04
0x34b655…2a6f
2 touches
0 conflicts
0x3145b8a3…e4d1
0x34b655…2a6f
2 touches
0 conflicts
0x74e62768…be3a
0x34b655…2a6f
2 touches
0 conflicts
0x767a3bb5…657a
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity