← previous blocknext block →recent activity
Analyzing
Block #107,451,190
14 transactions · 14 stateful · 2026-09-23 23:22:30 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,451,190 · 14 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
1w02w14w05w17w08w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd85c966d…f345
0x99c7a7…8bf0
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf51a94f0…f9b9
0x34b655…2a6f
4 touches
1 conflict
0xf798103c…0878
0x34b655…2a6f
4 touches
1 conflict
0x040740a5…29f6
0x754704…b603
4 touches
1 conflict
0x1004cdd3…ee46
0x754704…b603
4 touches
1 conflict
0x621762d2…9159
0x754704…b603
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xd85c966d06…3ef345
Audit this contract →
← previous block·next block →recent activity