← previous blocknext block →recent activity
Analyzing
Block #100,110,619
12 transactions · 12 stateful · 2026-08-29 06:17:15 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,110,619 · 12 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
2w03w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3dbeece…df7c
0x8964d7…10f8
4 touches
1 conflict
0xf3dbeece…df7f
0x8964d7…10f8
4 touches
1 conflict
0xf3dbeece…df80
0x8964d7…10f8
4 touches
1 conflict
0xf3dbeece…df82
0x8964d7…10f8
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xf3dbeeceba…11df7c
Audit this contract →
← previous block·next block →recent activity