← previous blocknext block →recent activity
Analyzing
Block #103,987,759
9 transactions · 9 stateful · 2026-09-11 20:12:12 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,987,759 · 9 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
2w05w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587dcf2c…7759
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x5c8a8db2…8a6d
0x34b655…2a6f
4 touches
1 conflict
0x0b70d0e9…ec09
0x34b655…2a6f
2 touches
0 conflicts
0x38c094c2…a251
0x34b655…2a6f
2 touches
0 conflicts
0x3b9ea80d…5471
0x34b655…2a6f
2 touches
0 conflicts
0x3e69adfb…3b62
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 0x587dcf2cff…267759
Audit this contract →
← previous block·next block →recent activity