← previous blocknext block →recent activity
Analyzing
Block #100,984,802
22 transactions · 15 stateful · 2026-09-01 07:39:45 UTC
Parallelism
91/100
Blocked
27%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,984,802 · 22 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
2w04w05w16w114w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…0007
0x067abd…3ea3
2 touches
0 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0x10d80fee…dbda
0x34ae4d…3fc5
2 touches
0 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
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 0xe5bb3628b5…71e5e8
Audit this contract →
← previous block·next block →recent activity