← previous blocknext block →recent activity
Analyzing
Block #106,337,024
28 transactions · 25 stateful · 2026-09-20 01:53:14 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,337,024 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w09w111w118w219w320w421w223w124w427w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47257d10…096f
0x34b655…2a6f
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
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
6 conflicts on slot 0x47257d1025…51096f
Audit this contract →
← previous block·next block →recent activity