← previous blocknext block →recent activity
Analyzing
Block #106,030,902
19 transactions · 19 stateful · 2026-09-19 00:12:35 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,030,902 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w18w213w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dac3b81…02ee
0x34b655…2a6f
4 touches
1 conflict
0xb6e0b4cf…e3a5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
2 touches
0 conflicts
0x0c60a6c2…3c67
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 0x9dac3b81e5…e602ee
Audit this contract →
← previous block·next block →recent activity