← previous blocknext block →recent activity
Analyzing
Block #103,216,307
27 transactions · 26 stateful · 2026-09-09 03:20:16 UTC
Parallelism
74/100
Blocked
27%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,216,307 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w012w213w219w020w323w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc95424fa…d221
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xfd1a5849…13e1
0x34b655…2a6f
4 touches
2 conflicts
0x2c45dc1d…9eca
0x34b655…2a6f
4 touches
1 conflict
0x977e7572…0efb
0x34b655…2a6f
4 touches
1 conflict
0xda3eb3c3…9d60
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity