← previous blocknext block →recent activity
Analyzing
Block #105,539,452
26 transactions · 23 stateful · 2026-09-17 06:56:34 UTC
Parallelism
92/100
Blocked
9%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,539,452 · 26 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
1w02w118w024w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0x8b71c68e…0f76
0x99c7a7…8bf0
4 touches
1 conflict
0xd0fa1733…0b67
0x754704…b603
4 touches
1 conflict
0x38d5c851…bf46
0x754704…b603
4 touches
1 conflict
0x2e618acf…234f
0x754704…b603
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity