← previous blocknext block →recent activity
Analyzing
Block #100,141,881
15 transactions · 12 stateful · 2026-08-29 08:54:48 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,141,881 · 15 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
1w03w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1e51be…2b9b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x883b1ea6…2acf
0x34b655…2a6f
4 touches
1 conflict
0xf2dc7074…4491
0x34b655…2a6f
4 touches
1 conflict
0x2a949bb2…8769
0x34b655…2a6f
2 touches
0 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x49900445…93ab
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
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 0x6d1e51be5e…5e2b9b
Audit this contract →
← previous block·next block →recent activity