← previous blocknext block →recent activity
Analyzing
Block #100,982,968
12 transactions · 10 stateful · 2026-09-01 07:30:31 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,982,968 · 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
2w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b26c372…ee7e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0002
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0004
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…000c
0x023eb9…b2b4
2 touches
0 conflicts
0x0b009709…9b7f
0x11ed3b…2c96
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 0x191e0467ba…1470e5
Audit this contract →
← previous block·next block →recent activity