← previous blocknext block →recent activity
Analyzing
Block #100,919,943
17 transactions · 16 stateful · 2026-09-01 02:13:30 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,919,943 · 17 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
1w02w14w07w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x62811193…1867
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186c
0x34ae4d…3fc5
2 touches
0 conflicts
0xd671bc34…553c
0x34ae4d…3fc5
2 touches
0 conflicts
0xd8fd2add…50fc
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 0xb5c7c6aad4…acfdba
Audit this contract →
← previous block·next block →recent activity