← previous blocknext block →recent activity
Analyzing
Block #93,441,429
16 transactions · 16 stateful · 2026-08-05 20:23:08 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,441,429 · 16 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
1w02w13w04w05w16w17w08w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd44e517e…8d2f
0x34b655…2a6f
4 touches
1 conflict
0x1ea2c53b…887a
0x754704…b603
4 touches
1 conflict
0x2edbccf6…cc14
0x754704…b603
4 touches
1 conflict
0x3d19ddf7…ac25
0x754704…b603
4 touches
1 conflict
0x140bbe18…6f47
0x99c7a7…8bf0
4 touches
1 conflict
0xa5b2d571…e945
0x99c7a7…8bf0
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: 0xe52b1424…bb7230
1 conflict on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity