← previous blocknext block →recent activity
Analyzing
Block #102,243,701
25 transactions · 23 stateful · 2026-09-05 17:27:07 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,243,701 · 25 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
2w03w04w17w29w314w016w117w119w020w122w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x738d841d…3c29
0x34b655…2a6f
6 touches
3 conflicts
0x25fd5528…ff50
0x34b655…2a6f
6 touches
3 conflicts
0x39a0c5a0…a992
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x540ce5b8…30b8
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity