← previous blocknext block →recent activity
Analyzing
Block #100,985,362
36 transactions · 21 stateful · 2026-09-01 07:42:34 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,985,362 · 36 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w010w014w015w118w119w223w024w128w229w230w331w133w434w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5db0ca44…afdf
0x34b655…2a6f
6 touches
3 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x68a05f4b…4f69
0xd32edf…ff58
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x641aed07…bcb9
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
3 conflicts on slot 0x5db0ca4484…26afdf
Audit this contract →
← previous block·next block →recent activity