← previous blocknext block →recent activity
Analyzing
Block #100,983,830
16 transactions · 14 stateful · 2026-09-01 07:34:52 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,983,830 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2fd6de4…1729
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xa7dcd6d9…a1ba
0x34b655…2a6f
4 touches
1 conflict
0x3e1b21c6…b1e4
0x34b655…2a6f
2 touches
0 conflicts
0x4786839b…c29a
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 0xd2fd6de4a1…5c1729
Audit this contract →
← previous block·next block →recent activity