← previous blocknext block →recent activity
Analyzing
Block #100,977,318
18 transactions · 16 stateful · 2026-09-01 07:02:06 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,977,318 · 18 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
2w03w112w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bb4d9a2…62bc
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
2 touches
0 conflicts
0x9343bf87…d5a4
0x34b655…2a6f
2 touches
0 conflicts
0x9ec251b7…7277
0x34b655…2a6f
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
1 conflict on slot 0x4bb4d9a256…f862bc
Audit this contract →
← previous block·next block →recent activity