← previous blocknext block →recent activity
Analyzing
Block #76,158,030
16 transactions · 13 stateful · 2026-05-22 01:03:00 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,158,030 · 16 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
5w06w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x25d593…7777
4 touches
1 conflict
0x00000000…0000
0x30611e…d8d9
4 touches
1 conflict
0x00000000…0002
0x30611e…d8d9
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x24cfe713…0f91
0x25d593…7777
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xe3ee7f9e…f356
0x3bd359…433a
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: SPIDERMON (SPIDERMON)
1 conflict on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity