← previous blocknext block →recent activity
Analyzing
Block #100,730,137
15 transactions · 14 stateful · 2026-08-31 10:18:19 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,730,137 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w110w111w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x330587fd…4cd7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0xebc2e0d7…958e
0x3bd359…433a
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
3 conflicts on slot 0x79347b2491…eb9fba
Audit this contract →
← previous block·next block →recent activity