← previous blocknext block →recent activity
Analyzing
Block #100,986,403
29 transactions · 25 stateful · 2026-09-01 07:47:48 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,986,403 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w07w08w19w010w113w014w119w220w222w123w324w225w327w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54c6fb44…369a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0x772cc8de…65e8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1d9c3f2e…88ea
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x3a5a5cc2…1e71
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
6 conflicts on slot 0x54c6fb4487…3b369a
Audit this contract →
← previous block·next block →recent activity